The design decision to not include

[dapper ore]

This is more a post for #┊・ontap-api . But we were told we needed none of this, and we were able to rework our Ansible Initial Setup playbooks to be 100% REST. What are you missing?

[zinc blade]

Rename Root Aggregats, Rename Root Volumes, Rename Management LIFs

[true silo]

Hello,

I can confirm that SVM root volume cannot be renamed.

This is breaking our internal naming scheme.

Not a big deal, but I wonder why such naming cannot be changed.

This probably reflects the underlyiung design which is based on wrong assumptions.

Regarding the REST API, I'am currently jungling between REST and ZAPI (for transition) and inside REST between rest_info, rest_cli and restit.

rest_cli is very special because it is not abiding any "standard".

rest_cli is not idempotent as ansible

rest_cli is not REST compliant because it does not send back the standard codes (200, 201, 400, 404, ...)

And this requires finding the correct values which is not possible without the current "channel"

I eventually completed the migration of the 2 automation process we have but this is fragile and suggest it will have to evolve again.