Discussion about optimization items in gray and beta configuration
In PR 13587, I discussed with @KomachiSion about optimization items in gray and beta configurations. I'm creating this issue for discussion and tracking.
- These 2 beta related issues 13585 13580 in Nacos V3. Do we need to do some related enhancements in V2?
I checked the code in v2.x-develop, the beta config deletion functionality works fine. The deletion is handled by deleteConfigGrayV1 properly in V2.
ConfigController#stopBeta -> ConfigOperationService#deleteConfig -> ConfigGrayModelMigrateService.deleteConfigGrayV1
- In Nacos v3, we can make the code more graceful. It seems that the beta table deletion can be handled by
deleteConfigGrayV1properly. Not sure why we remove it fromConfigControllerV3. Maybe we can usedeleteConfigGrayV1(dataId, group, namespaceId, BetaGrayRule.TYPE_BETA, null, null)inConfigControllerV3.
@shiyiyue1102 Do you have any insight into this? Should we do any enhancements in V2 and V3?
Grayscale compatibility mode is expected to be removed in several future versions, and can be optimized to facilitate future removal
Grayscale compatibility mode is expected to be removed in several future versions, and can be optimized to facilitate future removal
Is there anything I can do for Grayscale compatibility mode? Would you like me to optimize the item I mentioned above👆?
Grayscale
in future, all config operation logic should be uniformed to ConfigOperationService ,include ConfigControllerV3,If you are willing to help optimize it ,that would be great.
This issue has been open 30 days with no activity. This will be closed in 7 days.