squakez commented on PR #4942: URL: https://github.com/apache/camel-k/pull/4942#issuecomment-1840393778
An additional comment which may be useful in the future. Before reaching this state, I've worked on a few experiments. The result of them may return useful eventually. The first experiment was to let the operator assume the control of the managed fields of a Deployment: https://github.com/apache/camel-k/commit/1e4aaaaa5d6fde8aab49121ff666ef355b904279#diff-de2d026ce0dc415e68ee971f300e7320de019cc68c5171cf76425859587f1a85 - this solution was discarded because it clearly overlap the external deployment procedure (ie, triggering a new deployment). The second one had the same problem (overlapping external deployment): https://github.com/squakez/camel-k/tree/feat/it_import_delete_deploy - in this case we were deleting the deployment, in order to let the operator create and manage one from scratch. Although they are aggressive approaches, they may be used eventually in a sort of "dry-run" operation to let the user decide if a given deployment can be substituted with a managed Integration (at the price of forcefully deleting the original deployment). -- 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
