claudio4j commented on PR #5090: URL: https://github.com/apache/camel-k/pull/5090#issuecomment-1919274030
camel-k-runtime supports the dynamic reload of a route (no project rebuild) when the parameters are modified, for example, the master trait, if the [resourceName parameter change](https://github.com/apache/camel-k-runtime/blob/main/camel-k-master/impl/src/main/java/org/apache/camel/k/master/MasterContextCustomizer.java#L34) with a `-t master.resource-name=new-foo` , the master trait in camel-k-runtime is backed by camel-master and not [camel-quarkus-kubernetes](https://github.com/apache/camel-quarkus/blob/main/extensions/kubernetes/runtime/src/main/java/org/apache/camel/quarkus/component/kubernetes/cluster/KubernetesClusterServiceConfig.java#L107), so this means that when the user changes the `resource-name` parameter camel-k-runtime just reloads the route, however in camel-quarkus-kubernetes it requires a rebuild of the project due to [`ConfigPhase.BUILD_TIME`](https://quarkus.io/guides/writing-extensions#config-phases). I think this is fine, as there are only 3 extensions in camel-k-runtime whom are affected by this hot reload feature not available in non dev mode in camel-quarkus. -- 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
