[
https://issues.apache.org/jira/browse/CAMEL-18721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697926#comment-17697926
]
Claus Ibsen commented on CAMEL-18721:
-------------------------------------
We can possible have camel-jbang keep a special file up to date with current
running camel integration names.
Then if we can get the completion script to load from the file instead of
hardcoded values?
~/.camel/names
Then names is a text file with the current running names. When a camel is
stopped, then we need to update the file, in
camel-kamelet-main/camel-cli-connector.
> camel-jbang - name/pid completion for camel top/stop commands
> -------------------------------------------------------------
>
> Key: CAMEL-18721
> URL: https://issues.apache.org/jira/browse/CAMEL-18721
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
> Affects Versions: 3.19.0
> Reporter: Tadayoshi Sato
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> Similarly to CAMEL-18716, we can provide positional parameter completion for
> integration names and pids with {{camel top}} and {{{}camel stop{}}}:
> {code:java}
> $ camel top context [TAB]
> $ camel stop [TAB]
> {code}
> But implementing this should be a bit trickier as the completion script needs
> to call back {{camel ps}} to get completion candidates. We can embed the
> completion by using Picocli's {{@Parameters}} {{completionCandidates}}
> attribute.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
