gansheer commented on PR #4793: URL: https://github.com/apache/camel-k/pull/4793#issuecomment-1763946473
So let's recap a little: The solution proposed is to stop early on the process (before it get to the apply part) when the following conditions are ALL met: * Integration status contains a condition `IntegrationConditionKitAvailable` with status `Error` * Integration status phase is `Error` * IntegrationKit status phase is `Error` (the one declared by the Integration) From the [e2e test](https://github.com/apache/camel-k/pull/4815) I gathered the following: * an Integration with invalid or unknown dependencies : any fix will generate a new Integration Kit => solution OK * an Integration with unknown component in route : the IntegrationKit is not generated until all component are known => solution OK * an Integration with route compilation error : the IntegrationKit was already generated successfully and any change in the route won't have any impact on the IntegrationKit => solution OK I really don't see any use case where an IntegrationKit in Error will be able to recover without the creation of a new one. Is there such a process or something that could act directly on an IntegrationKit CR without acting from the Integration CR ? @squakez @lburgazzoli -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
