shuting 7282ecca9f fix: add skipBackgoundRequests to configure loop protection option (#9157) ... * fix typo Signed-off-by: ShutingZhao <shuting@nirmata.com> * add new attribute skipBackgroundRequests Signed-off-by: ShutingZhao <shuting@nirmata.com> * move to per rule config Signed-off-by: ShutingZhao <shuting@nirmata.com> * check flag Signed-off-by: ShutingZhao <shuting@nirmata.com> * clean up Signed-off-by: ShutingZhao <shuting@nirmata.com> * update docs Signed-off-by: ShutingZhao <shuting@nirmata.com> * fix logger Signed-off-by: ShutingZhao <shuting@nirmata.com> * add retryCount to ur.status Signed-off-by: ShutingZhao <shuting@nirmata.com> * add chainsaw tests Signed-off-by: ShutingZhao <shuting@nirmata.com> --------- Signed-off-by: ShutingZhao <shuting@nirmata.com>		2023-12-19 06:25:12 +00:00
..
cleanup.go	fix: generate policy fails if triggered resource name exceeds 63 characters limit (#8466)	2023-11-06 10:37:13 +00:00
clone.go	feat: Add support for server-side-apply in generate rules (#7705)	2023-08-02 17:59:37 +00:00
data.go	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
generate.go	fix: add skipBackgoundRequests to configure loop protection option (#9157)	2023-12-19 06:25:12 +00:00
response.go	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
source.go	fix: generate policy fails if triggered resource name exceeds 63 characters limit (#8466)	2023-11-06 10:37:13 +00:00
utils.go	fix: generate policy fails if triggered resource name exceeds 63 characters limit (#8466)	2023-11-06 10:37:13 +00:00
validate.go	refactor: engine pattern package and add duration support (#5958)	2023-01-10 14:07:26 +01:00
validate_test.go	refactor generate controller (#3589)	2022-04-13 12:45:04 +00:00