[FR] Resolve Smart Group Dependencies

[grahampugh]

Hi,

Since Jamf Pro 10.5, it's not been possible to copy objects that have unresolved dependencies. This is mostly solved by copying objects in such an order to prevent this, e.g. always copy categories and EAs first. Where this falls down is with smart groups. The result of which is that with many Jamf Pro instances, you have to keep running Replicator multiple times until all the dependencies for the Computer and Mobile Smart Groups are resolved.

I wonder if this could be made to happen automatically? I could envisage checking specifically for 409 responses during the copying process, and if at least one occurs, just automatically do a second pass for that endpoint, and keep going until there are no more 409s (up to a sensible maximum number of passes). I have a script that does something similar (less intelligently - it just does a number of passes that you can define).

Implementing this would make Replicator more likely to be a tool that you can just leave running and be reasonably confident that it will copy everything over without any more interaction needed.

[grahampugh]

As an update, I've implemented this now in my own migration script, and it's working pretty well. I also implemented it for the wipe option in that script, where a 400 response is an indicator of a dependency conflict.

[BIG-RAT]

Added a bit of logic to re-queue smart groups with nested group criteria when needed. As time permits let me know if that works.