I create Externalizer configuration kept in config.publish folder , then i override that value through AEM cloud environment variables , Its not pick whatever authored in environment config value
// Configuration created by Apache Sling JCR Installer
@BrianKasingli @aanchal-sikka @EstebanBustamante @Nishant-Singh @DPrakashRaj. @Sady_Rifat
How do you know that CM values are not being picked up? Is it falling back to default value from OSGI config?
once you add/update the CM values it take some time to get it updated on the environment approx 15 min.
Then I believe your config.publish OSGI config is not working. Can you check on developer console if you see your OSGI config for publisher and is it the custom service on which you are calling the externalizer for publish?
1. Please validate the configs locally, to verify that the config file has no issues. Also, please remove the extra "" in externalizer.domains
2. Once we have the configs in, we also need to make sure, we use the right API
@Reference Externalizer externalizer; Externalizer externalizer = resourceResolver.adaptTo(Externalizer.class); externalizer.publishLink(resolver, "/my/page") + ".html"; externalizer.authorLink(resolver, "/my/page") + ".html";
I set those environment variables through the command line local instance it's working fine.
But when we add those environments variables AEM cloud environment configuration, it's not picking values.