Andrea Cosentino created CAMEL-26619:
----------------------------------------
Summary: camel-azure-servicebus - run the integration tests on
Floci AZ
Key: CAMEL-26619
URL: https://issues.apache.org/jira/browse/CAMEL-26619
Project: Camel
Issue Type: Test
Components: camel-azure-servicebus
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Fix For: 4.24.0
Part of the move of the Azure test-infra to Floci AZ (CAMEL-26613).
The integration tests of camel-azure-servicebus ({{ServiceBusProducerIT}},
{{ServiceBusConsumerIT}}) run only with the connection string of a real
namespace ({{camel.component.azure-servicebus.connection-string}}), and create
their queues, topics and subscriptions with {{ServiceBusAdministrationClient}}.
Floci AZ emulates the Service Bus AMQP 1.0 data plane with an ActiveMQ Artemis
sidecar started through the Docker socket ({{mocked=false}}), with the
connection string
{{Endpoint=sb://<host>:<port>;...;UseDevelopmentEmulator=true}}. Queues, topics
and subscriptions, with sessions, can be declared up front in the official
emulator's {{Config.json}} format.
h4. Change
* Add a {{camel-test-infra-azure-servicebus}} module that starts Floci AZ with
the Docker socket mounted and the queues, topics and subscriptions the tests
use.
* Run the integration tests against it; keep the remote mode, where the tests
still create the entities.
* Skip the integration tests on ppc64le and s390x.
h4. Not covered
Floci AZ does not implement scheduled messages, deferred messages, session
state or rule management over AMQP. Tests that use them stay remote only.
Depends on CAMEL-26613.
_Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
