This documentation no longer appears to be available. Any chance there is an updated link?

Hi.I have heard it mentioned that Pipeline variables can be used in AEMaaCS to control things in dispatcher such as disabling the caching only in the dev environment.  Does anyone know how this can be done or can point to some documentation describling this? I accidentally posted this question under...

Hi.I have heard it mentioned that Pipeline variables can be used in AEMaaCS to control things in dispatcher such as disabling the caching only in the dev environment.  Does anyone know how this can be done or can point to some documentation describling this? ThanksYonit

How would you use environment variables to let's say disable cache for your dev environment.  Does this apply to AEM as a cloud service or only AMS. @Nupur_Jain @arunpatidar cc: @Deleted Account  

in order to get rid of the jacoco coverage error in this case, you need to add some tests for the added methods to MyProductTeaserImpl.java to  MyProductTeaserImplTest.java and this is not specified in the tutorial.

When trying to compile the venia example from https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content-and-commerce/storefront/developing/customize-cif-components.html?lang=en#bonus-challengegetting this errorRule violated for bundle venia.core: branches covered ratio is 0.37...

This was found to be a bug and a jira was created for it.Sling has logback integration for all logging-related activities.Date Pattern('.'yyyy-MM-dd-a ) is not treated as valid pattern in logback.[0].The corresponding bug has been raised in logback Jira - https://jira.qos.ch/browse/LOGBACK-1552Accor...

@pradeep1320668 What are you saying will not work?

If there is no explicit generation of two files, what exactly would be the significance of this pattern different than the daily one? Currently the data collected is exactly the same as the daily (from midnight to midnight) the only difference is the addition of AM or PM to the filename. It is clear...

Since you intend the osgi changes to persist, instead of trying to exclude it, make the config part of your code base.  Add the file under my.test.config.TestConfiguration.xml under /apps/test/config with the configuration values you want to persist: <?xml version="1.0" encoding="UTF-8"?><jcr:root x...