Croway opened a new pull request, #2102: URL: https://github.com/apache/camel-spring-boot/pull/2102
JIRA: [CAMEL-27061](https://issues.apache.org/jira/browse/CAMEL-27061) - Spring Boot ignores a property below a bound prefix when no field matches it. An option under a starter prefix that was removed or renamed therefore had no effect, and nothing was logged: `camel.springboot.*` (removed in 4.13), `camel.component.servlet.mapping.*`, `camel.component.{consul,file,jgroups.raft,kubernetes,zookeeper}.cluster.service.*`, `camel.service.lra.*`, `camel.component.undertow.spring.security.*`, `camel.supervising.controller.*`, `camel.dataformat.securexml.*`, `camel.dataformat.yaml-snakeyaml.*`, `camel.health.components-enabled` and `camel.health.config[id].*`. - The auto-configuration that reads the new prefix now logs a WARN at startup for each such property, with where it is set and the option to use instead: `CamelAutoConfiguration` (`camel.springboot.*`, `camel.supervising.controller.*`, the two data formats), `CamelHealthCheckAutoConfiguration`, `ServletMappingAutoConfiguration`, the Consul, file, JGroups Raft, Kubernetes and ZooKeeper cluster service auto-configurations, `LraServiceAutoConfiguration` and `UndertowSpringSecurityCustomizer`. The check is in the new `RemovedPropertiesHelper`. It reads the Spring Boot property sources, so environment variables and relaxed names are covered. Behaviour does not change: the old options are still not applied. - `camel-undertow-spring-security-starter` fails at startup when no provider is configured. Its error message named the old `camel.component.undertow.spring.security.provider.*` prefix, and now names `camel.security.undertow.<provider>.*`. - Not logged, as they are still read: `camel.springboot.lenient-configuration-binding`, and the data formats renamed in 3.15 by a dash only, such as `camel.dataformat.zipfile` for `camel.dataformat.zip-file` (Spring Boot ignores the dash). - The Spring Boot page lists the removed and renamed prefixes. The camel-mcp-server-starter tests now set `camel.main.run-controller` instead of the removed `camel.springboot.main-run-controller`. Tests: `RemovedPropertiesWarningTest` (camel-spring-boot), `ServletMappingRemovedPropertiesTest` (camel-servlet-starter), and a `*RenamedPropertiesTest` in each of the five cluster service starters, camel-lra-starter and camel-undertow-spring-security-starter. The WARN cases fail before (camel-spring-boot 12/15, each starter 1/2) and pass after; the controls (the current options are applied and not logged) pass both ways. No upgrade guide entry: only new WARNs, docs and a corrected error message. The camel docs fix for the same JIRA (the camel-test-spring example used `camel.springboot.name`) is apache/camel#30230. _Claude Code on behalf of Federico Mariani_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
