[
https://issues.apache.org/jira/browse/CAMEL-26616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26616.
---------------------------------
Resolution: Fixed
Merged in https://github.com/apache/camel/pull/29249 (0eebd4977602) for 4.24.0.
_Claude Code on behalf of davsclaus_
> camel-azure-cosmosdb - run the integration tests on Floci AZ
> ------------------------------------------------------------
>
> Key: CAMEL-26616
> URL: https://issues.apache.org/jira/browse/CAMEL-26616
> Project: Camel
> Issue Type: Test
> Components: camel-azure
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.24.0
>
>
> Builds on the Floci AZ container that CAMEL-26615 adds to
> {{camel-test-infra-azure-common}}.
> The integration tests of camel-azure-cosmosdb ({{CosmosDbProducerIT}},
> {{CosmosDbConsumerIT}} and the client, database and container operations
> tests) run only when {{-Dendpoint}} and {{-DaccessKey}} point at a real
> Cosmos DB account.
> Floci AZ emulates the Cosmos DB NoSQL API in process: databases, containers,
> items, SQL queries, patch and transactional batch. The Java SDK requires TLS
> in gateway mode, which Floci AZ serves with a self-signed certificate it
> generates at startup ({{FLOCI_AZ_TLS_ENABLED=true}}, certificate on
> {{/_floci/tls-cert}}).
> h4. Change
> * Add a {{camel-test-infra-azure-cosmosdb}} module: Floci AZ with TLS, the
> emulator account key, and a client that trusts the emulator certificate.
> * Run the producer and operations integration tests against it; keep the
> remote mode.
> * Skip the integration tests on ppc64le and s390x.
> h4. Not covered
> Floci AZ does not emulate the change feed, so {{CosmosDbConsumerIT}} (change
> feed processor) stays remote only. Stored procedures are stored but never run.
> Depends on CAMEL-26615.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
