add the nft processing queue name in configs

[cfaur09]

Reasoning

• At the moment the queue: 'api-process-nfts' is hardcoded in the code and the same rabbitmq cannot be used by 2 different api setups

Proposed Changes

• Add the queue name for nft process queue in configs

[IosifGabriel]

Hello, I still think there needs to be done some concatetation for the deadLetterExchange as it remained hardcoded

mx-api-service/src/main.ts

Line 129 in 5b0d9f1

deadLetterExchange: 'api-process-nfts-dlq',

mx-api-service/src/queue.worker/nft.worker/nft.worker.module.ts

Line 35 in 5b0d9f1

deadLetterExchange: 'api-process-nfts-dlq',

[cfaur09]

Hello, I still think there needs to be done some concatetation for the deadLetterExchange as it remained hardcoded

mx-api-service/src/main.ts

Line 129 in 5b0d9f1

deadLetterExchange: 'api-process-nfts-dlq',

mx-api-service/src/queue.worker/nft.worker/nft.worker.module.ts

Line 35 in 5b0d9f1

deadLetterExchange: 'api-process-nfts-dlq',

Solved 🟢

[tanghel]

I would make here a feature called "processNfts" and add there both the normal queue and the dead letter queue name. when reading the activation flag, try to read it first from features and then also from the "old" location to maintain backwards compatibility. update all config files with the new location. in this way we have all process nft-related functionality grouped together