Fix: Fixed global exchange name and updated database connection client 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.
This commit is contained in:
Davidson Gomes
2024-07-17 18:55:35 -03:00
parent 7e9132fcfe
commit b907d85a7e
3 changed files with 4 additions and 3 deletions

View File

@@ -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,