This was more of a vague thought. It's not good having to hack into internals like this.

The vague thought is if this subsystem is enabled, a DUP will attach ClusteredDeploymentRepository to the deployment. This means any DUP can look for it and if present use it. So, other clustering-related DUPs, the ones that set up all this stuff in the first place, could check for this attachment and if present populate it themselves. Instead of a separate DUP like you have in this patch having to analyze everything after the fact.

I have no idea if that is feasible or even a good idea, but it's something to keep in mind for the future.