Enhancements in 5.2.1

ORION-234157: Added an ability to associate the cluster with a Thales CipherTrust domain (other than the root domain). The following user controls have been added for this purpose:
- In VAST Web UI, the Auth Domain field in the Advanced Configurations -> Encryption tab of VAST Easy Install
- In VAST CLI, the --ekm-auth-domain option on the cluster create command
- In VAST REST API, the ekm_auth_domain parameter in POST requests to the /clusters/ endpoint.
Note that the domain must be created in Thales CipherTrust Manager prior to cluster deployment.
ORION-236934: Added an ability to connect the cluster to Thales CipherTrust Manager via an HTTP(s) proxy. To do so, use the following controls during cluster deployment:
- In VAST Web UI, the Use proxy flag that displays additional fields to specify the proxy in the Advanced Configurations -> Encryption tab of VAST Easy Install
- In VAST CLI, the --ekm-proxy-address option on the cluster create command
  Note
  When entering the command in the command line, a different spelling for the option is automatically suggested, --ekm-proxies, although the correct option keyword is --ekm-proxy-address.
- In VAST REST API, the ekm_proxy_address parameter in POST requests to the /clusters/ endpoint.
Added support for the following EKM providers:
- Fortanix Data Security Manager (DSM)
- HashiCorp Vault

ORION-219500: Enhanced NFS rquota implementation to support retrieving quota sizes that exceed 16TB.

ORION-212662: Added user controls to determine whether POSIX mode bits are inherited from the parent directory when using a view policy with NFS security flavor:
- In VAST Web UI, the Inherit ACL from parent option in the Permissions for New Files and Directories tab of view policy settings (Element Store -> View policies -> choose to create or edit a policy).
- In VAST CLI, the --enable-inherit-parent-mode-bits and --disable-inherit-parent-mode-bits options on the viewpolicy create and viewpolicy modify commands.

ORION-223116: Added an ability to configure the way the cluster handles SMB compound requests beginning with a CREATE request when the starting CREATE request gets a STATUS_PENDING response.
By default, the cluster sends STATUS_PENDING responses to all remaining requests in the compound, which may not be expected by the client.
You can alter this behavior so that the cluster will first respond with STATUS_PENDING only to the starting CREATE request (skipping the rest of the responses). After the entire compound is executed, responses to all requests in the compound will be sent. To alter the cluster behavior, contact VAST Support.

ORION-232589: Removed the limit of 256 characters for the webhook payload definition (in VAST Web UI: Settings -> Notifications -> Webhook Setup -> Webhook Data field).