When we move integration service to production, there needs to be a mechanism to be able to move changes to metadata from UAT to production. The UAT environment and the production environment will both be in production.
We currently do not have the ability to run the same module (say Goonj integration) from the same jvm pointing to two environments.
Story
The Goonj module in integration service needs to be able to run two instances in production - UAT and Prod - so that each can be configured to a different source environment and a different destination organisation/instance.
It should be possible to run just one of these instances if required
Solution
The problem here is that there is just one properties file that provides environment details. To fix this we can
Make the properties file from properties to yaml, start using lists instead. Also change deployment files in avni-infra and ensure that they work fine
Motivation
When we move integration service to production, there needs to be a mechanism to be able to move changes to metadata from UAT to production. The UAT environment and the production environment will both be in production.
We currently do not have the ability to run the same module (say Goonj integration) from the same jvm pointing to two environments.
Story
The Goonj module in integration service needs to be able to run two instances in production - UAT and Prod - so that each can be configured to a different source environment and a different destination organisation/instance.
It should be possible to run just one of these instances if required
Solution
The problem here is that there is just one properties file that provides environment details. To fix this we can