[I] Wildcards in Routes Sources [camel-k]
MotaOcimar opened a new issue, #4941: URL: https://github.com/apache/camel-k/issues/4941 ### 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: ```sh 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: ```sh kamel run --name=my-integration ./routes/* ``` ### Open questions _No response_ -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Wildcards in Routes Sources [camel-k]
squakez commented on issue #4941: URL: https://github.com/apache/camel-k/issues/4941#issuecomment-1832342936 Thanks for reporting. Feel free to contribute, it does seem a good first issue case. -- 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
Re: [I] Wildcards in Routes Sources [camel-k]
claudio4j commented on issue #4941: URL: https://github.com/apache/camel-k/issues/4941#issuecomment-1832358383 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. -- 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
Re: [I] Wildcards in Routes Sources [camel-k]
rinaldodev commented on issue #4941: URL: https://github.com/apache/camel-k/issues/4941#issuecomment-1861462007 @squakez @claudio4j can you assign this one to me? -- 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
Re: [I] Wildcards in Routes Sources [camel-k]
squakez commented on issue #4941: URL: https://github.com/apache/camel-k/issues/4941#issuecomment-1862314303 Done. Mind that we are under the effort to migrate the CLI to Camel JBang (see https://github.com/apache/camel/pull/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. -- 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
Re: [I] Wildcards in Routes Sources [camel-k]
squakez closed issue #4941: Wildcards in Routes Sources URL: https://github.com/apache/camel-k/issues/4941 -- 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
