Fix stale environment variables in AEM Cloud Manager
You update a configuration file in Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites, but some properties aren’t reflecting the changes. If a property previously used an environment variable or secret, and you replace it with a hardcoded value, AEM may still use the old reference. This happens because AEM prioritizes existing secrets over new hardcoded values. To fix this, remove or update unused secrets in Cloud Manager and redeploy your configuration.
Description description
Environment
Product: Adobe Experience Manager as a Cloud Service – Sites (AEMaaCS – Sites)
Environment Type: Development
Product Offering: Cloud Manager
Issue/Symptoms
- When updating a configuration file, changes to certain properties don’t take effect.
- If a property previously used an environment variable or secret, replacing it with a hardcoded value doesn’t override the old reference.
- The system continues to use the old secret even after deploying the updated configuration.
- This happens due to OSGi configuration interpolation, which prioritizes existing secrets over hardcoded values.
Resolution resolution
- Identify any environment variables or secrets previously used in your OSGi configurations, but are no longer needed.
- Go to Adobe Cloud Manager and locate these variables or secrets.
- Delete or update the unused entries directly in Cloud Manager.
- Redeploy your updated configuration file after making these changes.
Key Notes:
- There’s no cache to clear for OSGi configurations. AEM simply prioritizes existing secrets over hardcoded values.
- Remove any unused secrets or variables from Cloud Manager if your code no longer requires them.
By following these steps, you’ll ensure that your updated configurations work as expected.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f