AEM Cloud sites configuration properties merging from config.publish to config.publish.stage | Community
Skip to main content
sravs
Community Advisor
sravsCommunity Advisor
Community Advisor
June 18, 2026
Question

AEM Cloud sites configuration properties merging from config.publish to config.publish.stage

  • June 18, 2026
  • 2 replies
  • 11 views

When specific property is not explicitly deifned under config.publish.dev, the system automatically merges/inherits the property value defined under config.publish. 

Steps to Reproduce:

  1. Create a configuration with few values under config.publish.dev.
  2. Create a configuration with the same PID as defined earlier under config.publish, and update the values, include new property which was not defined as part of config.publish.dev.
  3. Deploy to cloud dev environment.
  4. Observe that the dev environment uses the value from config.publish while there is existing configuration file for config.publish.dev without any vlaue for the new property.

This issue occurs on all runmodes.

As per this document https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/configuring-osgi#runmode-resolution,

There is no property-level merging between runmode specific folders for the same PID. AEM selects only one configuration which is having most matching runmodes.

Please let me know if anyone encountered the same.

Thanks,

Sravani

2 replies

A
akhil_merupula
Level 4
June 19, 2026

Hi ​@sravs, this is expected behavior, not a bug.

 

AEM Cloud Service runmode resolution is winner-takes-all at the folder level, no property-level merging happens. The most specific matching folder wins entirely for that PID.

 

Correct pattern: Define all properties in config.publish as your baseline. In config.publish.dev, only override what differs. Any property missing from the winning folder falls back to the OSGi component’s @Designate defaults, not the parent runmode folder.

 

You can confirm which config “won” via /system/console/configMgr or the Cloud Manager Developer Console for publish tier.

sravs
Community Advisor
sravsCommunity AdvisorAuthor
Community Advisor
June 20, 2026

Hi ​@akhil_merupula,

Thanks for your reply.

It appears that any property not explicitly defined under config.publish.dev is being inherited from config.publish. I have verified this in the developer console configuration, where the effective configuration reflects a combination of values from both config.publish.dev and config.publish.

If this inheritance behavior is the intended default behavior, could you please share any relevant documentation or official reference that describes it? Having such documentation would be helpful for validation and future reference.

Thanks.

Terms & ConditionsAccessibility statement

Loading footer...