[
https://issues.apache.org/jira/browse/CAMEL-22288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-22288.
---------------------------------
Resolution: Fixed
> camel-jbang: Kubernetes plugin: add --source-dir option
> -------------------------------------------------------
>
> Key: CAMEL-22288
> URL: https://issues.apache.org/jira/browse/CAMEL-22288
> Project: Camel
> Issue Type: New Feature
> Components: camel-kubernetes
> Reporter: Cameron Fitzwater
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.14.0
>
>
> Similar to `camel run`, it would be nice to have a `camel kubernetes
> run/export --source-dir` option.
> --source-dir=<sourceDir>
> Source directory for dynamically loading Camel
> file
> (s) to run. When using this, then files cannot
> be specified at the same time.
> The goal being, if a directory has numerous `*.yaml` files AND an
> `application.properties` file alongside, one should be able to easily just
> specify the directory.
> What is driving this was a slight issue when trying to determine how to
> include *all* things from a source directory, and the fact that the
> application.properties files was not being picked up unless I first `cd` into
> the source-dir. This may be a potentially separate issue, but is related to
> why this feature request is being floated.
> ```
> kubernetes export raw/* \
> --name=$(APP_NAME) \
> --dir=./$(APP_NAME) \
> --gav=org.example.project:$(APP_NAME):0.0.0 \
> --image='ghcr.io/org/$${project.artifactId}:$${revision}' \
> --image-builder=docker \
> --clean-dir \
> --runtime=quarkus
> ```
> ... however, if you `cd ./raw` and run this, it does pick the
> `application.properties` file up:
> ```
> cd ./raw
> kubernetes export * \
> --name=$(APP_NAME) \
> --dir=../$(APP_NAME) \
> --gav=org.example.project:$(APP_NAME):0.0.0 \
> --image='ghcr.io/org/$${project.artifactId}:$${revision}' \
> --image-builder=docker \
> --clean-dir \
> --runtime=quarkus
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
