[
https://issues.apache.org/jira/browse/CAMEL-22517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028757#comment-18028757
]
Pasquale Congiusti edited comment on CAMEL-22517 at 10/9/25 12:46 PM:
----------------------------------------------------------------------
Thanks for all the comments. I think indeed that a balance is required.
Probably the questions we should ask are different: do we really need this (or
any other) CLI? or is it just syntactic sugar? is it a user tool or a developer
tool? does it exist any alternative around? if needed, could it be part of a
"plugin" based approach instead (as already suggested)?
Dropping some code into a project is a commitment for long term maintenance
that will end up on the shoulder of the future maintainers of such a project. I
advocate to keep adding as much as we can (which is one of the reason of Camel
success), but we need to do it in a sustainable manner.
The main concern why I started CAMEL-22501 is that from a vulnerability point
of view we already have many potential open doors (main classes) that could be
exploitable. I suggest to consider the tradeoff of the benefit of adding
anything new vs the potential surface area of a vulnerabilities.
was (Author: squakez):
Thanks for all the comments. I think indeed that a balance is required.
Probably the questions we should ask are different: do we really need this (or
any other) CLI? or is it just syntactic sugar? is it a user tool or a developer
tool? does it exist any alternative around? if needed, could it be part of a
"plugin" based approach instead (as already suggested)?
Dropping some code into a project is a commitment for long term maintenance
that will end up on the shoulder of the future maintainers of such a project. I
advocate to keep adding as much as we can (which is one of the reason of Camel
success), but we need to do it in a sustainable manner.
The main concern why I started CAMEL-22501 is that from a vulnerability point
of view we already have many potential open doors that could be exploitable. I
suggest to consider the tradeoff of the benefit of adding anything new vs the
potential surface area of a vulnerabilities.
> Expose Camel PQC capabilities via a CLI
> ---------------------------------------
>
> Key: CAMEL-22517
> URL: https://issues.apache.org/jira/browse/CAMEL-22517
> Project: Camel
> Issue Type: New Feature
> Reporter: Federico Mariani
> Priority: Minor
>
> It would be useful to expose some of the Camel PQC features via a CLI, like
> we did for jasypt
> https://camel.apache.org/components/4.14.x/others/jasypt.html#_tooling
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
