Describe the bug
Currently, for example if a subnet is fetched based on name and cluster_name in filters, ntnx_subnets_info doesn't consider both filter. (i.e. "AND" behaviour)
To Reproduce
Steps to reproduce the behavior:
Run playbook task:
ntnx_subnets_info:
filter:
name: <vlan_name>
cluster_name: <cluster name>
register: result
This playbook fetches all subnets from cluster name given.
Expected behavior
Info module should consider all filters for fetching entities.
Describe the bug Currently, for example if a subnet is fetched based on name and cluster_name in filters, ntnx_subnets_info doesn't consider both filter. (i.e. "AND" behaviour)
To Reproduce Steps to reproduce the behavior: Run playbook task:
This playbook fetches all subnets from cluster name given.
Expected behavior Info module should consider all filters for fetching entities.