shuting 0c3351887a fix: the same source cannot be used for multiple targets with a generate clone rule (#7436) ... * add source labels to targets Signed-off-by: ShutingZhao <shuting@nirmata.com> * handle multiple triggers/targets for the same clone source Signed-off-by: ShutingZhao <shuting@nirmata.com> * add source labels to targets Signed-off-by: ShutingZhao <shuting@nirmata.com> * fix test Signed-off-by: ShutingZhao <shuting@nirmata.com> * remove unused code Signed-off-by: ShutingZhao <shuting@nirmata.com> * add kuttl tests Signed-off-by: ShutingZhao <shuting@nirmata.com> * rename the test Signed-off-by: ShutingZhao <shuting@nirmata.com> * add kuttl tests Signed-off-by: ShutingZhao <shuting@nirmata.com> * add kuttl tests Signed-off-by: ShutingZhao <shuting@nirmata.com> * split apiversion label into version and group Signed-off-by: ShutingZhao <shuting@nirmata.com> --------- Signed-off-by: ShutingZhao <shuting@nirmata.com>		2023-06-07 13:50:47 +00:00
..
clusterpolicy	fix: the same source cannot be used for multiple targets with a generate clone rule (#7436)	2023-06-07 13:50:47 +00:00
policy	fix: array element removal should be synced to the downstream resource with a generate data sync rule (#7417)	2023-06-06 12:07:07 +02:00
validation	Remove policy validation prevent loop for generate (#7388)	2023-06-02 13:53:16 +02:00