After setting up my (first) Launch Cloud Service, it looks like the AEM Author environment is linked to my Launch Staging embed code and the AEM Publish environment to the Launch Production embed code.
Is it the expected design?
Let's say I have 3 AEM instances, Dev, Staging and Prod.
I would like the AEM Dev instance to be tied to the Dev Launch embed code for both environments (Author and Publish).
I would like the AEM Staging instance to be tied to the Staging Launch embed code for both environments (Author and Publish).
And I would like the AEM Production instance to be tied to the Launch Staging embed code for AEM Author and Production Launch embed code for AEM Publish, which is the current design.
We had similar issue with the DTM Cloud Service but at least, we were able to override these settings in the DTM cloud service UI.
How can I do this with the Launch Cloud Service? Do we need to alter these settings in the CRXDE directly?
Would be really great if we could map each AEM instance to whatever Launch embed code we want, directly in the Cloud Service UI.
Unless I'm missing something?
Thanks,
Olivier