analog reef
Hi everybody,
I wrote a script to automate vscan config and set use_rest: always.
When executing it, it seems that zapi is used instead of rest, why?
TASK [Create and enable Scanner pool] *********************************************************************************************************************************************
task path: /home/myuser/ansible/vscan/main.yml:23
ok: [localhost] => (item={'hostname': 'toaster', 'vserver': 'myvserver', 'pool': 'mypool', 'user': 'DOMAIN\user', 'scanners': 'x,y,z'}) => {"ansible_loop_var": "item", "changed": false, "item": {"hostname": "toaster", "pool": "mypool, "scanners": "x,y,z", "user": "DOMAIN\user", "vserver": "myvserver"}, "warnings": ["With version 22.0.0 ONTAPI (ZAPI) has been deprecated. The final ONTAP version to support ZAPI is ONTAP 9.13.1. ZAPI calls in these modules will continue to work for ONTAP versions that supports ZAPI. You can update your playbook to use REST by adding use_rest: always to your playbook. More information can be found at: https://github.com/ansible-collections/netapp.ontap", "Using ZAPI for netapp.ontap.na_ontap_vscan_scanner_pool, ignoring 'use_rest: always'."]}
[WARNING]: With version 22.0.0 ONTAPI (ZAPI) has been deprecated. The final ONTAP version to support ZAPI is ONTAP 9.13.1. ZAPI calls in these modules will continue to work for
ONTAP versions that supports ZAPI. You can update your playbook to use REST by adding use_rest: always to your playbook. More information can be found at:
https://github.com/ansible-collections/netapp.ontap
[WARNING]: Using ZAPI for netapp.ontap.na_ontap_vscan_scanner_pool, ignoring 'use_rest: always'.
PLAY RECAP ************************************************************************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
netapp.ontap collection 22.9.0 is used
brittle narwhal