#ZAPI or REST API

1 messages · Page 1 of 1 (latest)

vivid lodge
#

Hi there,
I’m working on a PowerShell script that uses the DataONTAP PowerShell toolkit. The plan is to use the REST API in the script to make it ready for the EOA of the ZAPI. I am not sure what the best way is to convert over to the REST API and if it is needed, or if the installation of the NetApp.ONTAP PowerShell module could remove the need to switch over all together. Does the PowerShell toolkit use the REST API and if yes, is it backwards compatible with older scripts?

grand rune
#

NetApp did the conversion in the background. So the most current version of the Powershell module should use REST API if the ONTAP version is ready for it. From my experience some things do break because the APIs are not 100% identical in features.
You can get it from the PS Gallery: https://www.powershellgallery.com/packages/NetApp.ONTAP/

NetApp.ONTAP 9.13.1.2306

NetApp.ONTAP PowerShell Toolkit. The ONTAP 9.13.1 PowerShell Toolkit provides end-to-end automation and enables more efficient and scalable administration of NetApp storage. This module contains over 2340 PowerShell cmdlets to help you automate ONTAP administration on FAS and AFF systems, commodity hardware, and the cloud. This toolkit also supp...

vivid lodge
crimson jewel
#

Using modules like this provides a layer of abstraction that, unless you’re forcing a specific protocol/style, the general practice is for the module on the client to negotiate with the server. Also, MAJOR +1 to get it from the powershell gallery. The release cadence is much faster than the binary installers provided through the NetApp Support Site. I’m not certain the patch releases of the module get released via binary…