With the rest API you can also pass in | NetApp | Page 1

young violet Oct 5, 2022, 6:49 AM

#

Hmm ok, I'll check it out. Thanks!

#

Btw, I think there's a typo in the documenation for the "na_ontap_user_role" module, it says:

state
Whether the specified > user < should exist or not.

#

I could not get your example to work, specifying something other than an API URI gives the error:
"Specified URI path is invalid or not supported."
Any idea?

#

Also, I can't get the "command_directory_name" keyword to work.. so totally lost here

cloud linden Oct 5, 2022, 3:56 PM

#

What version of ONTAP are you using?

young violet Oct 6, 2022, 6:54 AM

#

ONTAP 9.10

cloud linden Oct 6, 2022, 4:08 PM

#

Can you show me your playbook.

The command part the /security/roles REST api was only added in 9.11.1 so you'll need to have
use_rest: never in your playbook to fall back to zapi

young violet Oct 7, 2022, 9:37 AM

#

    netapp.ontap.na_ontap_user_role:
      hostname: "{{ item }}"
      state: present
      name: log_viewer
      privileges:
      - path: DEFAULT
        access: none
      #command_directory_name: DEFAULT
      #access_level: none
    loop: "{{ clusters }}"```

#

So I updated a cluster to 9.11 and this seems to work now on there but not the rest
Perhaps you know of a way to do conditional if ONTAP version is greater than 9.10 ?
Or some other way to handle this since I really want to use REST

#With the rest API you can also pass in