nacos-go-sdkv2.0 changed the semantics of namingclient.RegisterInstance, resulting in each RegisterInstance() overwriting the entire nacos service instead of appending an Instance.
I think this is an unreasonably breaking change of nacos-go-sdk, and perhaps nacos-go-sdk rather than dubbogo should be the one to fix it.
There's another API in Nacos 2.x, something like batchRegister to register all protocol instances at once. I think dubbo-go can try to support this change in Nacos 2.x.
Environment
Issue description
nacos-go-sdkv2.0 changed the semantics of namingclient.RegisterInstance, resulting in each RegisterInstance() overwriting the entire nacos service instead of appending an Instance.
I think this is an unreasonably breaking change of nacos-go-sdk, and perhaps nacos-go-sdk rather than dubbogo should be the one to fix it.
Logs
Click me to check logs
``` Copy logs to here. ```