[
https://issues.apache.org/jira/browse/CAMEL-21238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884255#comment-17884255
]
Thomas Diesler edited comment on CAMEL-21238 at 9/24/24 12:30 PM:
------------------------------------------------------------------
PR: https://github.com/apache/camel/pull/15672
The suggested change takes a fresh look at k8s run --dev, it detail ...
- the export directory is different for each reload
- avoid duplicate labels (due to reexport)
- pod logging is more lenient and patiently waits for the reloaded pod (as for
the original)
- file watching a setup anew for the reloaded project
was (Author: tdiesler):
PR: https://github.com/apache/camel/pull/15672
The suggested change takes a fresh look at k8s run --dev, it detail ...
- the export directory is different for each reload
- duplicate labels (due to reexport) are avoided
- pod logging is more lenient and patiently waits for the reloaded pod (as for
the original)
- file watching a setup anew for the reloaded project
I tested with
https://github.com/tdiesler/camel-cloud-examples/tree/main/quarkus/timer-log
> camel-jbang - k8s run - Reloading project does not change route behaviour
> -------------------------------------------------------------------------
>
> Key: CAMEL-21238
> URL: https://issues.apache.org/jira/browse/CAMEL-21238
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Major
> Fix For: 4.9.0
>
>
> When running a project with `--dev` like this ...
> {code}
> jbang camel kubernetes run timer-log-route.yaml --logs --dev \
> --gav=examples:timer-log:1.0.0 \
> --trait container.imagePullPolicy=IfNotPresent \
> --trait service.type=NodePort \
> --runtime=quarkus
> {code}
> I see ...
> {code}
> Reloading project due to file change: timer-log-route.yaml
> {code}
> without image re-build/deploy
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
