The AMQP protocol is used to receive messages from the following channels:

• VirtualTopic.services.partner-entitlement-gateway
• VirtualTopic.canonical.operationalProduct
• VirtualTopic.services.productservice.Product
• VirtualTopic.canonical.subscription

These are mostly configured in swatch-contracts.

The problem is that we don't have an AMQP broker instance in ephemeral that we could use for testing (for producing messages and verify that these messages are consumed by our services).

At the moment, we have been verifying these integrations by exposing an API for test purposes only where we put the message on, and this API simulates the message arrival. However, this approach does not guarantee that the AMQP configuration works, so we might miss important issues in production.

Another workaround we have in place, is to configure our AMQP consumers to be kafka consumers because we have a Kafka instance we can use, and we have IQE utilities to send messages to topics.

However, the correct solution is to setup an AMQP broker for ephemeral (we can use active MQ, rabbitmq, artemis, ...), configure our services to communicate with this instance, and IQE tests to send messages over to it.

Acceptance Criteria

• Set Up an AMQP broker for ephemeral deployments only: we should use artemis and setup a new GitHub repository for this.
• Create IQE tooling to send messages over AMQP
• Revert the changes in https://github.com/RedHatInsights/rhsm-subscriptions/pull/4495, and configure the connectors to use the AMQP broker from ephemeral.
• Tests created as part of https://issues.redhat.com/browse/SWATCH-3456 should keep working after switching to AMQP.