GRANITE-45463: update the default FileVault version to 1.3.2 #1091
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As described here: #1087, this PR aims to update the default FileVault version to 1.3.2.
Related Issue
The related issue is: #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: