manic bolt
Hello,
We are trying to move our new automation from ZAPI to REST due to the future of ZAPI is to be deprecated but we are finding many cases in which the modules from ZAPI works in a different way that REST does so this is very disruptive for us. Why the modules don't work as the same way? This is a big change for us since we need to refactor the code. Has anybody using the user module with REST?
Thanks.
raw whale
Hi, here's an example how the application_dicts parameter works with REST (assuming use_rest: always, username, password and hostname are set via module_defaults):
- name: Create testuser
netapp.ontap.na_ontap_user:
state: present
name: testuser
application_dicts:
- application: http
authentication_methods: password
- application: ssh
authentication_methods: password
- application: ontapi
authentication_methods: password
role_name: admin
Hello Jan,
Thanks for share an example, but my doubt is: this is work as it does ZAPI? Because when we use this module the behaviour isn't the same.
raw whale
It does not work the same as with ZAPI. The API endpoint for users using REST can be viewed here: https://docs.netapp.com/us-en/ontap-restapi/ontap/security_accounts_endpoint_overview.html
There is also a ZAPI to REST mapping documentation available at https://docs.netapp.com/us-en/ontap-restmap/security.html
