You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been learning how to use KCL function. And it's great thanks a lot)! But I've bumped into not very neat behavior, if KCL exits with an error function is immediately reevaluated and this pollutes info logs. I wonder if this case is specific to the KCL function only or it's crossplane composite functions architecture feature. Btw I haven't noticed this type of behaviour with patch-and-transform function.
Have you tried the function-go-templating? The logic of retry is not determined by KCL itself, and I seem to have not found how to set the retry time in the function.
No, I haven't tried( Let's try to ask @ytsarev . Yury would you mind please sharing your suggestion? What's the best way to handle the delay, should it be inside the KCL function implementation, or maybe the function should return 0 code? The later of course would be odd, however if functions successfully exist crossplane doesn't immediately re-evaluate them, kinda odd mitigation...
Hello @Peefy,
I've been learning how to use KCL function. And it's great thanks a lot)! But I've bumped into not very neat behavior, if KCL exits with an error function is immediately reevaluated and this pollutes
info
logs. I wonder if this case is specific to the KCL function only or it's crossplane composite functions architecture feature. Btw I haven't noticed this type of behaviour with patch-and-transform function.Here's the example:
To suppress immediate reevaluation and logs pollution I have to manually guard resource creation. Is this expected behavior?
The text was updated successfully, but these errors were encountered: