Since in AEM cloud custom runmode are not supported so how we can detect that which environment it is since AEMCaaS give feasibility to detect dev/stage/prod but what about UAT and QA ?
Solved! Go to Solution.
Views
Replies
Total Likes
while you always implement code like suggested by @narendiran_ravi , I would like to understand why you need to that distinction.
If you need to configure different OSGI configuration for DEV and UAT (which is a DEV in AEM CS terms), you can manage them through environment variables. See https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dep...
You can use the Cloud environment variables and update this for specific environments. This can be assigned to an OSGI config variable.
{
"environmentType":"$[env:ENVIRONMENT_TYPE]"
}
Hi @pratikshah
Please check osgi config for Env indicator: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-use-aem-environm...
Hi @pratikshah,
to achieve this you will need to create custom configuration for your different DEV environments and set DEV/QA/INT as environment variable. For example, your configuration might look like this:
{
"instanceEnvironment": "$[env:INSTANCE_ENVIRONMENT;default=dev]",
"instanceType": "author"
}
Hope this helps,
Daniel
@pratikshah Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
while you always implement code like suggested by @narendiran_ravi , I would like to understand why you need to that distinction.
If you need to configure different OSGI configuration for DEV and UAT (which is a DEV in AEM CS terms), you can manage them through environment variables. See https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dep...
Views
Likes
Replies
Views
Likes
Replies