Closed steffenvan closed 5 months ago
Please rather update to the most recent 1.3.4.
@vladbailescu I see that this is still open. Can we have a review on this? This causes disruption for several customers (and us because we have to fix it).
superseded by https://github.com/adobe/aem-project-archetype/pull/1177
Description
As described here: https://github.com/adobe/aem-project-archetype/issues/1087, this PR aims to update the default FileVault version to 1.3.2.
Related Issue
The related issue is: https://github.com/adobe/aem-project-archetype/issues/1087
Motivation and Context
Whenever a new CM environment is set up, it should employ the latest version of FileVault, 1.3.2 as of today. One reason is that it fixes https://jira.corp.adobe.com/browse/GRANITE-45463. In short, upgrading to the newest FileVault enables the deployment of custom and/or customized OOTB index definitions. Without the latest version, customers will need to manually upgrade FileVault whenever they receive a new CM environment.
How Has This Been Tested?
By upgrading the FileVault to 1.3.2 on a dev CM environment and executed the pipeline with invalid and valid
Screenshots (if appropriate):
Types of changes
Checklist: