vmware_content_library_info: Only lists Content Libraries with the type of "Local", does not include "Subscribed" type

[mikepruett3]

SUMMARY

When using the vmware_content_library_info task type to query our Content Libraries, only the Libraries with the type of "Local" are reported back to the ansible task. We used shared or "Subscribed" Content Libraries in our environment, to share a consistent Library of VM Templates between all of our vCenters.

How can we get this functionality added?

ISSUE TYPE

• Bug Report

COMPONENT NAME

vmware_content_library_info

ANSIBLE VERSION

ansible 2.10.9
  config file = /home/<redacted>/.ansible.cfg
  configured module search path = ['/home/<redacted>/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/<redacted>/.local/lib/python3.8/site-packages/ansible
  executable location = /home/<redacted>/.local/bin/ansible
  python version = 3.8.10 (default, Jun 22 2022, 20:18:18) [GCC 9.4.0]

COLLECTION VERSION

# /usr/local/lib/python3.8/dist-packages/ansible_collections
Collection       Version
---------------- -------
community.vmware 1.10.0

# /home/<redacted>/.local/lib/python3.8/site-packages/ansible_collections
Collection       Version
---------------- -------
community.vmware 1.10.0

CONFIGURATION

DEFAULT_HOST_LIST(/home/<redacted>/.ansible.cfg) = ['/home/<redacted>/inventory']
DEFAULT_LOG_PATH(/home/<redacted>/.ansible.cfg) = /home/<redacted>/.ansible/logs/log.txt
DEFAULT_TIMEOUT(/home/<redacted>/.ansible.cfg) = 120
DEFAULT_VAULT_PASSWORD_FILE(/home/<redacted>/.ansible.cfg) = /home/<redacted>/playbooks/secret.yaml

OS / ENVIRONMENT

vCenter Version - 7.0.3 build 20150588
Client - vSphere Client version 7.0.3.00700
Hosts - VMware ESXi, 7.0.3, 20036589

STEPS TO REPRODUCE

    - name: "Collect list of Content Libraries from specified vCenter"
      community.vmware.vmware_content_library_info:
        hostname: "{{ hostname }}"
        username: "{{ username }}"
        password: "{{ password }}"
        validate_certs: no
      register: libraries

    - name: "Display list of found Content Libraries"
      debug:
        var: libraries

EXPECTED RESULTS

TASK [Display list of found Content Libraries] ****************************************************************************************************************************
ok: [localhost] => {
    "libraries": {
        "changed": false,
        "content_libs": [
            "6b5e0c60-3173-4a75-8101-33335f3bb7dd",
            "7bd40369-84d6-4fd5-9cf9-7c33377f3931"
        ],
        "failed": false
    }
}

ACTUAL RESULTS

TASK [Display list of found Content Libraries] ****************************************************************************************************************************
ok: [localhost] => {
    "libraries": {
        "changed": false,
        "content_libs": [
            "6b5e0c60-3173-4a75-8101-33335f3bb7dd"
        ],
        "failed": false
    }
}

[mariolenz]

1.10.0 is quite old...

However, it looks like vmware_content_library_info still doesn't know about subscribed content libraries in the latest release. I'll try to work on this, but you probably would have to update to (at least) community.vmware 2.9.0.

edit: I think we could use the Content Subscribed Library APIs to achieve this.

[mariolenz]

@mikepruett3 Would it be possible for you to test PR #1437? I hope it will fix the issue.