Fix: Fixed global exchange name and updated database connection clien…

…t name

This commit resolves an issue with the global exchange name and updates the database connection client name. The `.env.example`, `CHANGELOG.md`, and `src/api/integrations/rabbitmq/libs/amqp.server.ts` files were modified. The exchange name in the AMQP server and global queues initialization has been changed to use the value from the configuration service. Additionally, the database connection client name has been updated in the `.env.example` file. The change in the `CHANGELOG.md` file has been updated accordingly.

.env.example

@@ -20,7 +20,7 @@ PROVIDER_PREFIX=evolution
 DATABASE_ENABLED=true
 DATABASE_PROVIDER=postgresql
 DATABASE_CONNECTION_URI='postgresql://user:pass@localhost:5432/evolution?schema=public'
-DATABASE_CONNECTION_CLIENT_NAME=evolution
+DATABASE_CONNECTION_CLIENT_NAME=evolution_exchange
 DATABASE_SAVE_DATA_INSTANCE=true
 DATABASE_SAVE_DATA_NEW_MESSAGE=true
 DATABASE_SAVE_MESSAGE_UPDATE=true

CHANGELOG.md

@@ -5,6 +5,7 @@
 * Fixed the function of saving or not saving data in the database
 * Resolve not find name
 * Removed DEL_TEMP_INSTANCES as it is not being used
+* Fixed global exchange name
 
 # 2.0.1-beta (2024-07-17 17:01)
 

src/api/integrations/rabbitmq/libs/amqp.server.ts

@@ -23,7 +23,7 @@ export const initAMQP = () => {
           return;
         }
 
-        const exchangeName = 'evolution_exchange';
+        const exchangeName = configService.get<Rabbitmq>('RABBITMQ').EXCHANGE_NAME || 'evolution_exchange';
 
         channel.assertExchange(exchangeName, 'topic', {
           durable: true,
@@ -59,7 +59,7 @@ export const initGlobalQueues = () => {
 
     const queueName = `${event.replace(/_/g, '.').toLowerCase()}`;
     const amqp = getAMQP();
-    const exchangeName = 'evolution_exchange';
+    const exchangeName = configService.get<Rabbitmq>('RABBITMQ').EXCHANGE_NAME || 'evolution_exchange';
 
     amqp.assertExchange(exchangeName, 'topic', {
       durable: true,