#na_ontap_snapmirror Not supporting identity preserve with REST API.
1 messages · Page 1 of 1 (latest)
from this doc - https://docs.netapp.com/us-en/ontap-restmap-9121/snapmirror.html#snapmirror-create
identity-preserve
No REST Equivalent
Identity preservation for an SVM DR relationship is part of the SnapMirror policy associated with the SnapMirror relationship.
above is from 9.11.1 REST API documentation
above is from 9.12.1 documentation
it is a support parameter
Important notes
The property "transfer_schedule" if set on a SnapMirror relationship overrides the "transfer_schedule" set on the policy being used with the SnapMirror relationship.
The property "throttle" if set on a SnapMirror relationship overrides the "throttle" set on the policy being used with the SnapMirror relationship.
The properties "transfer_schedule" and "throttle" are not supported when "restore" is set to "true".
The property "transfer_schedule" cannot be set to null (no-quotes) during SnapMirror relationship POST.
The property "throttle" is not supported when "create_destination.enabled" is set to "true".
The property "identity_preservation" is applicable to only SnapMirror relationships with SVM endpoints and it indicates which configuration of the source SVM is replicated to the destination SVM.
There is a gap between ZAPI to REST API documentation and REST API swagger documentation
In REST its no more identity_preserve it's identity_preservation with list of options to support it
we have identity_preservation option in na_ontap_snapmirror_policy module.
does using the policy created with identity_preservation in snapmirror module achieves same as identity_preserve in ZAPI?
Customer is using MirrorAllSnapshotsDiscardNetwork that is provided with ONTAP
checking with team as we might end up with duplicate options in 2 modules
With this policy MirrorAllSnapshotsDiscardNetwork, snapmirror relationship doesn't show that identity preserve is enabled
tracked with DEVOPS-5913