Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

config.author.prod or config.prod.author?

TB3dock
Level 7
Level 7

when setting up osgi configs, you put them in a dir to target a particular env and type.

The problem is that cloud and non cloud seem to have different behavior.

 

Should it be config.author.prod or config.prod.author?

 

We see both in various posts.  we are using config.prod.author for example.  This works fine on non cloud AEM, but on cloud AEM, it doesn't.

 

Or maybe the issue is that we have "default" osgi configs in /config, which we then assume will be overridden by config files in say /config.prod or /config.prod.author.  Is this assumption incorrect?  I.e. if we want a config applied to a specific env, we must not have it also in a more generic env? 

1 Accepted Solution
shikhasoni1
Correct answer by
Level 1
Level 1

Hi @TB3dock,

In case of AEM as a cloud service, you need to create it as config.(author/publish).(dev/qa/stage/prod).

 

Thanks

View solution in original post

5 Replies
kishorekumar14
Level 8
Level 8

Hi @TB3dock ,

 

Below format is the right one for AEMaaCS.

 

 

/apps/example/config.<author|publish>.<dev|stage|prod>

 

Actual syntax is

 

config.<service>.<environment_type>

 

  • service - author / publish
  • environment_type - dev,stage,prod

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/conf... 

 

If you configure it like above it will pick the right Osgi run mode config, else it will fallback to generic.

Bimmi_Soi
Community Advisor
Community Advisor

Hi @TB3dock ,

 

You need to create as config.(author|publish).(dev|qa|stage|prod) in AEM as a cloud service. PFB the image

Bimmi_Soi_0-1631699684862.png

 

Hope this helps!!!

 

Thanks!!!

Rohit_Negi550
Level 4
Level 4

Hi @TB3dock ,

 

Answering your query, The best match or the most match configuration will be taken

Eg:

If you have some configuration say /config.prod== abc

And /config.prod.author == def

And if the runmode of your instance have both prod and author in it then "def" configuration will take priority as it has more matches with run mode.

 

On Cloud check if correct run modes are set or not. 

 

Thanks!

ArunaSurukunta
Level 4
Level 4

@TB3dock ,

 

Runmode resolution can be done based on the node pattern that we create under apps. Below pattern of configuration should work fine in AEM Cloud and AEM instances.

 

/apps/example/config.<author|publish>.<dev|stage|prod>/

Please find the documentation here : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/co...

 

ArunaSurukunta_0-1631721950220.png

 

shikhasoni1
Correct answer by
Level 1
Level 1

Hi @TB3dock,

In case of AEM as a cloud service, you need to create it as config.(author/publish).(dev/qa/stage/prod).

 

Thanks

View solution in original post