Additional supported parameters needed in REST | NetApp | Page 1

dry owl Apr 1, 2025, 2:49 PM

#

Hi,
We're currently automating our environment with Ansible and are running into a couple of places where REST doesn't allow us to pass certain parameters:

module: na_ontap_net_port
parameters:

mtu
speed_admin
autonegotiate_admin

module: na_ontap_net_ifgrp
parameters:

name

I'd like to formally request these parameters be supported via REST so that we can manage these resources via Ansible

hollow elbow Apr 1, 2025, 4:28 PM

#

I really don't understand why they don't simply use the same source as base for their REST APIs as for the CLI commands. They already have all commands, parameters etc. in an XML format anyway (which they use to generate the CLI commands and the manual pages, for example) but still every REST API is hand-generated... no wonder things fall through the cracks here and there

long pulsar Apr 1, 2025, 7:19 PM

#

oh yes. I've been playing hell with API stuff and CVO for a few months now and it is very.. very frustrating

hollow elbow Apr 1, 2025, 8:04 PM

#

also, a lot of day-0 stuff is basically impossible since you cannot see/manage system objects (nodes, root aggregates, system SVMs, cluster LIFs, etc)

#Additional supported parameters needed in REST