knockknock10 commented on issue #6943: URL: https://github.com/apache/camel-k/issues/6943#issuecomment-6873109264
Thanks for the detailed explanation, @squakez. I understand your point about the current declarative approach. Simply stopping the remaining post-actions after a deployer error could leave resources partially updated, which may put the Integration in an even less consistent state. I agree that tracking the previous state and rolling back resources if an application fails would be a more complete approach. I'll look into how we can handle partial failures, restore previously applied resources, and prevent GC from running when the deployment cannot be completed. I'll work on this and open a draft PR so we can discuss the implementation and any edge cases. Also, I wanted to ask about contributing to other open issues in Camel K. I noticed there are some open issues that currently have no assignee. Would it be okay if I picked them up one at a time, after checking with you first? I'll avoid the 3.x milestone issues you previously advised me not to work on, as well as issues that are already assigned or being worked on by someone else. Thanks again for the guidance. -- 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]
