When ha-set actor is created, it creates a consumer bridge for DashHaGlobalConfig, which is the same name created by Dpu actor. The consumer bridge is designed to have only one destination to send update. If 2 consumer bridges are created with same name, it seems the second will shadow the first one. We can create multiple instances with different service path to allow them coexist. Or we can create a shared one with multiple destinations. Or we can have only one and let DPU to relay the update to ha-set.
When ha-set actor is created, it creates a consumer bridge for DashHaGlobalConfig, which is the same name created by Dpu actor. The consumer bridge is designed to have only one destination to send update. If 2 consumer bridges are created with same name, it seems the second will shadow the first one. We can create multiple instances with different service path to allow them coexist. Or we can create a shared one with multiple destinations. Or we can have only one and let DPU to relay the update to ha-set.