oscerd opened a new pull request, #25932:
URL: https://github.com/apache/camel/pull/25932
Adds a `=== camel-spring-boot` section to `camel-4x-upgrade-guide-4_23.adoc`
covering six starter defaults that
change in camel-spring-boot for 4.23. Docs only — no code in this repository
is touched.
The camel-spring-boot upgrade notes live here rather than in that
repository, following the precedent of
`=== camel-spring-boot - Duration configuration properties` in the 4.22
guide.
| Note | camel-spring-boot PR | JIRA |
|---|---|---|
| jolokia binds to loopback; cross-origin rejected |
apache/camel-spring-boot#1915 | CAMEL-24554 |
| vault/secrets starters fail closed on early resolution |
apache/camel-spring-boot#1900 | CAMEL-24508 |
| undertow-spring-security validates issuer and audience |
apache/camel-spring-boot#1910 | CAMEL-24497 |
| platform-http enforces `fileNameExtWhitelist` |
apache/camel-spring-boot#1897 | CAMEL-24496 |
| security policy sees environment variables | apache/camel-spring-boot#1913
| CAMEL-24503 |
| String conversions to file-backed types blocked |
apache/camel-spring-boot#1912 | CAMEL-24504 |
Each note says what changed, why, and how to opt back in where an opt-out
exists
(`camel.component.jolokia.server-config.host`,
`camel.vault.ignore-resolution-failures`,
`camel.security.undertow.keycloak.validate-audience`).
**Timing:** those PRs are open, not yet merged. This is deliberately a
companion rather than a follow-up, so
the notes are ready to land alongside them — but it should **not** merge
before they do, and if review changes
any opt-out property name I will update this to match. Only CAMEL-24499 from
that batch has merged, and it
needs no note (a serialization filter fix with no user-facing behaviour
change).
Two of the six are the ones most likely to surprise an operator:
- **jolokia** — a Kubernetes deployment scraping the agent over the pod
network will lose it until
`camel.component.jolokia.server-config.host` is set. The note calls that
out specifically.
- **security policy** — an application on `camel.security.policy=fail` that
configures Camel through the
environment may now fail startup on a violation that was always present
but previously invisible.
--
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]
