Is there a good place to see the REST replacements for deprecated modules? For example netapp.ontap.na_ontap_file_directory_policy: is a module we use quite regularly but I only see messages that it is being deprecated.
I don't want to resort to using CLI unless it is necessary, but I am finding the examples for many new modules to be a bit anemic in the official ansible module docs. I am still new to a lot of this so any resources would be greatly appreciated.
#This might be a silly question.
1 messages · Page 1 of 1 (latest)
Hello everyone. First day on here of course I posted before I said hello lol. My apologies.
github - https://github.com/ansible-collections/netapp.ontap
ansible-galaxy - https://galaxy.ansible.com/netapp/ontap
format is little better in github.
deprecated modules do not have REST equivalent.
na_ontap_file_directory_policy dont have REST equivalent.
but a policy is created automatically when configuring Security descriptor and Access control entries using na_ontap_file_security_permissions module. policy created are not visible to users.
its a good question.
We currently create a policy, then a security descriptor then a task that is referenced when we assign permissions. I am stuggling with all of this at the moment.
Also I am new to clusters and have been tasked with porting over code so I may get some of this worked out today. Thank you the link helped a lot. But the new modules in rest are not very close to what the modules they replaced are in ansible.
na_ontap_file_directory_polic is ZAPI only module, it does not have REST equivalent.
na_ontap_file_security_permissions is a different module, you can check how REST implements in this doc
https://library.netapp.com/ecmdocs/ECMLP2884821/html/index.html
look for DOC /protocols/file-security/permissions/{svm.uuid}/{path}
I am trying to apply the DACL to a security descriptor for a task. I see SLAG mentions them but it does not have an example of how to specify one.
I got some of it
I am trying to translate from REST to the fomat ansible is expecting
That may clear it up a bit.
there is an internal story already available for adding more examples in module documentation.
vserver: "{{ vserver}}" owner: "{{ owner }}", group: "{{ groups }}", access_control: slag, path: "/", acls: - access_control: slag access: access_allow rights: modify user: "{{ owner }}", apply_to: files: true this_folder: true sub_folders: true