From 1790a6cf7b3465d4964c7d17a8b0e96a7c9a3427 Mon Sep 17 00:00:00 2001 From: Jonny Mccoubrey Date: Fri, 2 Feb 2024 11:41:29 +0000 Subject: [PATCH 1/3] Update release notes --- release-notes-8.0.0.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/release-notes-8.0.0.md b/release-notes-8.0.0.md index 0180125b8..967ee394c 100644 --- a/release-notes-8.0.0.md +++ b/release-notes-8.0.0.md @@ -4,9 +4,9 @@ ${version-number} #### New Features -- **US857114**: Introduced `CAF_RABBITMQ_PROTOCOL` environment variable so that RabbitMQ URL protocol is customisable. - This allows for TLS-enabled connections to be made to RabbitMQ if desired. - By default, this variable is set to "amqp" so there is no change in behaviour unless specified. +- **US857114: Introduced configurable Rabbit MQ protocol so that, if desired, Rabbit MQ communication can be TLS enabled. + When using `cfg~caf~worker~RabbitConfiguration`, the protocol used by workers can be configured using the + CAF_RABBITMQ_PROTOCOL environment variable. The default value is 'amqp'. - **US857114:** Quorum queues leveraging 'x-delivery-count' for the handling of poison messages. #### Bug Fixes @@ -18,5 +18,9 @@ ${version-number} #### Breaking Changes - **US749035**: Classic queues and priority queues are deprecated, priority queues can still be created however it is no longer possible to publish messages with a priority. - When using `cfg~caf~worker~RabbitConfiguration.js`, the type of queue created by workers can be controlled by the ENV - CAF_RABBITMQ_QUEUE_TYPE, this currently defaults to 'quorum', but will be removed in a future release. + When using `cfg~caf~worker~RabbitWorkerQueueConfiguration.js`, the type of queue created by workers can be controlled + by the ENV CAF_RABBITMQ_QUEUE_TYPE, this currently defaults to 'quorum', but will be removed in a future release. +- **US857114**: Consumers using the util-rabbitmq module will need to handle additional exceptions when creating a + Rabbit MQ connection through `RabbitUtil.java`. If creating a Rabbit connection using default configuration, where + previously host, port, user and pass were provided, protocol will now also be required. + From f196b244ef7f476f073c028a14f35351ecb0bd34 Mon Sep 17 00:00:00 2001 From: Jonny Mccoubrey Date: Fri, 2 Feb 2024 12:12:32 +0000 Subject: [PATCH 2/3] Update release notes --- release-notes-8.0.0.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/release-notes-8.0.0.md b/release-notes-8.0.0.md index 967ee394c..00d43cc2a 100644 --- a/release-notes-8.0.0.md +++ b/release-notes-8.0.0.md @@ -4,9 +4,6 @@ ${version-number} #### New Features -- **US857114: Introduced configurable Rabbit MQ protocol so that, if desired, Rabbit MQ communication can be TLS enabled. - When using `cfg~caf~worker~RabbitConfiguration`, the protocol used by workers can be configured using the - CAF_RABBITMQ_PROTOCOL environment variable. The default value is 'amqp'. - **US857114:** Quorum queues leveraging 'x-delivery-count' for the handling of poison messages. #### Bug Fixes @@ -20,7 +17,10 @@ ${version-number} longer possible to publish messages with a priority. When using `cfg~caf~worker~RabbitWorkerQueueConfiguration.js`, the type of queue created by workers can be controlled by the ENV CAF_RABBITMQ_QUEUE_TYPE, this currently defaults to 'quorum', but will be removed in a future release. -- **US857114**: Consumers using the util-rabbitmq module will need to handle additional exceptions when creating a - Rabbit MQ connection through `RabbitUtil.java`. If creating a Rabbit connection using default configuration, where - previously host, port, user and pass were provided, protocol will now also be required. +- **US857114**: Introduced configurable Rabbit MQ protocol so that, if desired, Rabbit MQ communication can be TLS + enabled. When using `cfg~caf~worker~RabbitConfiguration`, the rabbit protocol used by services can be configured using + the CAF_RABBITMQ_PROTOCOL environment variable. The default value is 'amqp'. + Consumers using the util-rabbitmq module will need to handle additional exceptions when creating a Rabbit connection + through `RabbitUtil.java`. If creating a Rabbit connection using default configuration, where previously host, port, + user and pass were provided, protocol will now also be required. From e9d8cbb0682ecd8d28267987ef4e384d577f55c7 Mon Sep 17 00:00:00 2001 From: Jonny Mccoubrey <44871582+jonny-mccoubrey@users.noreply.github.com> Date: Fri, 2 Feb 2024 12:22:37 +0000 Subject: [PATCH 3/3] Update release-notes-8.0.0.md --- release-notes-8.0.0.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/release-notes-8.0.0.md b/release-notes-8.0.0.md index 00d43cc2a..9e7e55bd3 100644 --- a/release-notes-8.0.0.md +++ b/release-notes-8.0.0.md @@ -21,6 +21,5 @@ ${version-number} enabled. When using `cfg~caf~worker~RabbitConfiguration`, the rabbit protocol used by services can be configured using the CAF_RABBITMQ_PROTOCOL environment variable. The default value is 'amqp'. Consumers using the util-rabbitmq module will need to handle additional exceptions when creating a Rabbit connection - through `RabbitUtil.java`. If creating a Rabbit connection using default configuration, where previously host, port, - user and pass were provided, protocol will now also be required. + through `RabbitUtil.java`. RabbitUtil.createRabbitConnection now requires a protocol argument.