ibm.storage_virtualize.ibm_svcinfo_command module to have filtervalue options available for use

The ability to have the filtervalue option available would enable searching through lsvdisk to be a much more efficient when it comes to utilising the Ansible Collection. It would reduce the dependency on having to handle the large output from an lsvdisk command that currently presents issues with Ansible Tower and allow us to narrow down the set considerably, ensuring that we produce more readable Ansible Code.

The benefits would be realised by others who are embarking on an Infrastructure as Code journey, essentially allowing users the same functionality that they currently see from CLI and Python to be used via Ansible.

The way it would work is instead of gathering the total output of the lsvdisk command and pulling out the necessary data that we are looking for we could use a simple command with -filtervalue.

Current

- name: Get vdisk_UID Details
  ibm_svcinfo_command:
    command: "svcinfo lsvdisk"
    clustername: "{{ ibm_url }}"
    username: "{{ ansible_user }}"
    password: "{{ ansible_password }}"
  register: lsvdisk_output
  
- set_fact:
    volume_name: "{{ lsvdisk_array | selectattr('vdisk_UID', 'search', item.sample_lun_id) | map(attribute='name') }}"
    relationship_name: "{{ lsvdisk_array | selectattr('vdisk_UID', 'search', item.sample_lun_id) | map(attribute='RC_name') }}"
    iogrp: "{{ lsvdisk_array | selectattr('vdisk_UID', 'search', item.sample_lun_id) | map(attribute='IO_group_id') }}"
    mdiskgrp: "{{ lsvdisk_array | selectattr('vdisk_UID', 'search', item.sample_lun_id) | map(attribute='mdisk_grp_id') }}"

Proposed

- name: Get vdisk_UID Details
  ibm_svcinfo_command:
    command: "svcinfo lsvdisk -filtervalue vdisk_UID=<VDISK_UID>"
    clustername: "{{ ibm_url }}"
    username: "{{ ansible_user }}"
    password: "{{ ansible_password }}"
  register: lsvdisk_output