Typically the ideal scenario is to have one installation of the Solution Manager to access different environments such as SIT, UAT and PROD. This will allow to promote the changes from one environment to another using single instance of Solution Manager.
However, if the company policy does not allow access across environments, how do we promote from one environment to another? For example, I am not allowed to access UAT and PROD enviormnents from SIT and vice versa. How can I promote from SIT to UAT and then from UAT to PROD environment?
I can think of one option as below:
Install the Solution Manager in all 3 environments (SIT,UAT,PROD). Create a Revision in the SIT environment. Download the VQL file from SIT environment. Access the UAT environment and create a revision using the VQL file from the SIT environment. Perform the deployment in the UAT environment using this revision.
And I guess the same can be done to promote from UAT to the PROD environment by downloading the VQL file from UAT environment and then importing in the PROD environment to perform the deployment.
Please advise what would be the right way to promote under such scenarios where cross environment access is not allowed.
I would also like to ask about the Denodo License usage under such scenario. Typically the global license file is a multi-license file with the licenses for all 3 environments in one file. However if cross environment access is not allowed, does that mean I need to get 3 separate licenses one each for SIT, UAT and PROD, which also means that I need to install 3 instances of the Solution Manager and install the license for each environment separately?
