GRANITE-45463: update the default FileVault version to 1.3.2

steffenvan commented 1 year ago

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.

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

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

kwin commented 1 year ago

Please rather update to the most recent 1.3.4.

steffenvan commented 5 months ago

@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).

buuhuu commented 5 months ago

superseded by https://github.com/adobe/aem-project-archetype/pull/1177

adobe / aem-project-archetype