-
Notifications
You must be signed in to change notification settings - Fork 34
Upgrading to version 4.4.0
RabbitMQ has been removed from this new version in favour of Spring's event system. The new solution is self-contained and does not need to be configured.
- If you were using a standalone version of RabbitMQ, feel free to disable and remove it
- If you were using the containerized version provided with the previous releases, this change will be automatic when the Docker image is rebuilt
In order to rebuild the Docker image and set everything up, download the changes from this version and:
- Wait for any RabbitMQ queues to be empty
- Stop the connector with
./gradlew dockerComposeDown
- Build the new image with
./gradlew buildDockerCompose
- Start the new connector version with
./gradlew dockerComposeUp
Properties related to RabbitMQ have been removed. No changes are required to accomodate anything else to the new solution, but some references may remain in your system's environment variables. We encourage you to remove them as they no longer serve any purpose.
The following properties have been removed from infrastructure/src/main/resources/infrastructure.properties
. These were bound to the specific RabbitMQ of your system and were linked to environment variables, which can also be safely deleted.
-
spring.rabbitmq.password
->${PAYPAL_RABBITMQ_HOST:queue}
-
spring.rabbitmq.port
->${PAYPAL_RABBITMQ_PORT:5672}
-
spring.rabbitmq.username
->${PAYPAL_RABBITMQ_USERNAME}
-
spring.rabbitmq.password
->${PAYPAL_RABBITMQ_PASSWORD}
Properites related to RabbitMQ queues have been removed from the project and are no longer needed.
-
invoices/src/main/resources/invoices.properties
invoices.payments.queue
-
kyc/src/main/resources/kyc.properties
kyc.users.hyperwallet.queue
kyc.business.stakeholders.hyperwallet.queue
-
notifications/src/main/resources/notifications.properties
notifications.exchange
notifications.payments.queue
notifications.users.kyc.queue
notifications.business.stakeholders.kyc.queue