Croway opened a new pull request, #2087: URL: https://github.com/apache/camel-spring-boot/pull/2087
Fixes two groups of failures in the [Camel-Spring-Boot Daily main build #456](https://ci-builds.apache.org/job/Camel/job/Camel-Spring-Boot%20Daily/job/main/456/testReport/). Both came from Camel core 4.24.0-SNAPSHOT changes, not from changes in this repository. ### CAMEL-25675: Hashicorp Vault TLS options apache/camel@6362d0a5bfdd added `trustStore`, `trustStorePassword`, `keyStore` and `keyStorePassword` to `HashicorpVaultConfiguration`, together with the `cert` login. `VaultConfigurationPropertiesMappingTest` then failed because the starter did not expose them. - `HashicorpVaultConfigurationProperties` gets the four options as `camel.vault.hashicorp.trust-store`, `trust-store-password`, `key-store` and `key-store-password`. `HashicorpVaultAutoConfiguration` copies them onto the Camel configuration by name. - `authentication` now lists `cert`, matching Camel core. - `spring-boot.json` regenerated. ### CAMEL-26776: namespaced keys on shared state-store backends apache/camel@2948bb6308fb made the `state-store` component store keys on a shared `KeyValueRepository` (auto-discovered or `backend=#ref`) under `statestore:<storeName>:<key>`. Two tests in `SpringCacheStateStoreAutoConfigurationTest` still read the raw key, so they got `null`. - `camelRepositoryIsUsedWhenSpringCacheIsDisabled` and `springFactoryAndCamelRepositoryCoexist` now expect the namespaced key and no raw key. - New test `camelRepositoryKeysAreNotNamespacedWhenNamespacedIsDisabled` checks that `camel.component.state-store.namespaced=false` keeps the Camel 4.23 un-namespaced keys. This is the opt-out described in the 4.24 upgrade guide. ### Not in this PR - The 67 `camel-jsonpath-starter` failures and `SpringBootPlatformHttpCamelIntegrationsTest` fail with `NoClassDefFoundError: com/jayway/jsonpath/spi/json/Jackson3JsonProvider`. Since CAMEL-22857, `camel-jsonpath` needs json-path 3.0.0, but Spring Boot 4.1.x manages 2.10.0. Spring Boot 4.2 manages 3.0.0 (spring-projects/spring-boot#50786), so these will be handled with the Spring Boot 4.2 upgrade (CAMEL-26590). - `CassandraComponentConsumerIT.testConsumeUnprepared` timed out once while setting up the test and passed in builds 450 to 455. ### Tests Run locally against the current Camel 4.24.0-SNAPSHOT: - `core/camel-spring-boot`: `VaultConfigurationPropertiesMappingTest` (8/8) and the Hashicorp vault tests pass. - `components-starter/camel-state-store-starter`: all 27 unit tests pass. The Redis IT was not run. _Claude Code (Opus 5.5) 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]
