[
https://issues.apache.org/jira/browse/CAMEL-23181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065335#comment-18065335
]
Claus Ibsen commented on CAMEL-23181:
-------------------------------------
All of Camels properties are named camel.main.xxx camel.component.xxx and so
forth. There are hardly any camel.quarkus specific etc.
In the camel-catalog you can find all these property names
[https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/main/camel-main-configuration-metadata.json]
However beware that camel.server.xxx and camel.management.xxx are specific to
camel standalone / jbang only. Not for SB/Q. They have their own configuration
for their HTTP server and management capabilitties.
> [camel-jbang-mcp] Add camel_properties_translate tool
> ------------------------------------------------------
>
> Key: CAMEL-23181
> URL: https://issues.apache.org/jira/browse/CAMEL-23181
> Project: Camel
> Issue Type: Improvement
> Reporter: Luigi De Masi
> Assignee: Andrea Cosentino
> Priority: Minor
>
> During runtime migrations (e.g., Spring Boot → Quarkus),
> application.properties entries need to change prefixes, naming conventions,
> and sometimes keys entirely. AI agents currently do this by guessing, which
> leads to broken configurations.
> Add a camel_properties_translate tool that takes a set of configuration
> properties and translates them from one runtime to another.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
