You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user seeking simplicity in Camel K Integration configuration,
I want the ability to create Integrations from all files in a directory using a wildcard,
so that I can avoid dealing with a lengthy command line or multiple lines in the kamel-config.yaml file.
Problem
When we have several source files we end up with a huge command line (or several lines in the kamel-config.yaml file).
For example:
kamel run --name=my-integration ./routes/file1.xml ./routes/file2.xml ./routes/file3.xml ./routes/file4.xml
Proposal
This could be extremely simplified with a wildcard.
For the example shown previously, we could have the following:
kamel run --name=my-integration ./routes/*
Open questions
No response
The text was updated successfully, but these errors were encountered:
At least in linux when you use the wildcard, bash does the completion expansion and your example actually works.
However I am unsure about wildcard expansion in windows or macos.
Done. Mind that we are under the effort to migrate the CLI to Camel JBang (see apache/camel#12474). However I think it is still a good exercise to get used to the source code and be able to do other contributions. Thanks.
rinaldodev
added a commit
to rinaldodev/camel-k
that referenced
this issue
Jan 2, 2024
Requirement
As a user seeking simplicity in Camel K Integration configuration,
I want the ability to create Integrations from all files in a directory using a wildcard,
so that I can avoid dealing with a lengthy command line or multiple lines in the kamel-config.yaml file.
Problem
When we have several source files we end up with a huge command line (or several lines in the kamel-config.yaml file).
For example:
Proposal
This could be extremely simplified with a wildcard.
For the example shown previously, we could have the following:
kamel run --name=my-integration ./routes/*
Open questions
No response
The text was updated successfully, but these errors were encountered: