Closed seenkail closed 8 months ago
@seenkail i would reach out to the ONTAP REST API team on Netapp discord channel on this.
Currently the POST for LDAP does not support a name. https://library.netapp.com/ecmdocs/ECMLP2885799/html/#/name-services/ldap_create
Summary
As NetApp ZAPI coming end of life after ontap version 9.13.1, how we are going to use "name" variable in na_ontap_ldap_client as name variable is supported only in ZAPI.
Name variable is a key value in ldap client creation as it's a ldap client config name which must be there in order for the configuration to be successful.
Component Name
na_ontap_ldap_client
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
when we run the playbook using ZAPI we give the Name variable for client config. If we just go for use_rest : always , Name variable can't be used as its available only zapi. Since there is no Name variable in rest for na_ontap_ldap_client, Task creates the Client config name as vserver name , that's not a valid configuration . We need to specify the client config name for a valid configuration. Can we enhance this
Expected Results
Client config name should be something we give not the vserver name itself
Actual Results