knockknock10 commented on issue #6943: URL: https://github.com/apache/camel-k/issues/6943#issuecomment-6737220243
> I think we don't do any update operation at all. When there is a change to a resource, we patch it instead. You may try to reproduce by testing the patch maybe and see if it still applies. I tried reproducing it through the Patch path as suggested. The `ServerOrClientSideApplier` does call `Patch()`. One detail I found is that Camel K's fake client implements Patch by trying Create first and falling back to Update when the resource already exists. So I injected the failure at that fallback Update operation. The test passes and verifies that `Apply()` returns the simulated Deployment application error, but the previous generation's Deployment is still deleted. So the behaviour is reproducible through the applier's Patch path as well. I'll keep the fake-client implementation detail in mind when interpreting the result. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
