Rampai94

Rolling updates are possible due to the composite node store feature in Oak.

The mutable content is installed at three different times during the deploy phase in the pipeline:

Ahead of startup of new version of application:

index definitions (add, modify, remove)
During startup of new version of application but ahead of switchover:

Service Users (add)

Rampai94

https://express.adobe.com/page/O8ouF761akUN6/

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/introduction
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/what-is-new-and-different
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/aem-version-updates
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/overview

Rampai94

/*This method is used to Query the JCR and find results as per the Query.*/
def buildQuery(parent) {
    def queryManager = session.workspace.queryManager;
    def statement = 'select * from [nt:file] as t where ISDESCENDANTNODE(['+parent+']) AND NAME() LIKE \'%.jpg\'';
    queryManager.createQuery(statement, 'JCR-SQL2');
}

final def query = buildQuery(<replace_parent_path_here>);
final def result = query.execute()

Rampai94

Rampai94

Rampai94

Rampai94

Rampai94

Rampai94

Rampai94