AMF today only allows users to delete SI if all SI Dependency objects (safDepend) related to the SI are deleted first. The CCB will be rejected if users delete both SI and safDepend objects in the same CCB.
There's a model migration use case that needs to delete all SIs and all related safDepend in the same CCB, provided that all SIs are unassigned.
This ticket enables this use case.
(to be updated)
attach version 1, works with LOCKED all nodes/su/si
Attach updated AMF PR doc for this ticket
develop:
commit acc519ca87bcec8d35cd9665ad2a385ef17aceb6
Author: Minh Chau minh.chau@dektech.com.au
Date: Wed Oct 11 11:20:00 2017 +1100
amf: Allow SI and SI Dependency object to be deleted in same ccb [#2585]
documentation:
changeset: 219:995485d47ca9
tag: tip
user: Minh Hon Chau minh.chau@dektech.com.au
date: Wed Oct 11 11:37:27 2017 +1100
summary: amf: Update PR doc for deletion of SI and SI Dependency in same CCB
Related
Tickets:
#2585