Control the order in which objects are created/updated/deleted during a sync

[dgarros]

Environment

• DSync version: master

Proposed Functionality

Allow users to control the order in which objects are created/updated/deleted during a sync.
This logic could be different per type of object (device, interface etc ..)

Use Case

In some cases the order in which objects are created on a remote system is important because one object can be dependent on another one.
For example, if we have a list of interfaces, with a lag interface and 2 lag members, we need to ensure that the lag interface
gets created first but deleted last.

[itdependsnetworks]

Would it be more accurate to say set a priority?

Also, if I understand correctly this implies queuing on potentially the entire sync process plan is built?

Just trying to make sure I understand

[glennmatthews]

Would this logic be set by the source DSync, the target DSync, each source DSyncModel, each target DSyncModel, or what?

[dgarros]

@itdependsnetworks I think setting a priority would be different but I like the idea, it would be a lighter solution to influence the order in which things are processed.

@glennmatthews initially I was thinking if could be implemented at the DSync level, similar to what we are doing for the crud methods but since we are moving this part to the DSyncModel, it could make sense to implement this one there as well.