Merge pull request #62 from ZertoPublic/RecoveryReport

Remove -VpgIdentifier Parameter from Get-ZertoRecoveryReport function

RELEASENOTES.md

@@ -2,9 +2,4 @@
 
 ### Zerto Virtual Manager
 
-* [Zerto version 7.5 has been released.](https://s3.amazonaws.com/zertodownload_docs/Latest/Zerto%20Virtual%20Replication%20Release%20Notes.pdf) As part of this release Zerto has added API functionality that requires the following updates.
-  * A token is now required to pair two sites together. The need is discussed in [Issue 46](https://github.com/ZertoPublic/ZertoApiWrapper/issues/46). To implement this change a `-token` parameter has been added to the `Add-ZertoPeerSite` function.
-  * A new function has been added; `New-ZertoPairingToken`. This function will allow users to generate a pairing authentication token from the target ZVM to be used in the pairing process. [Issue 47](https://github.com/ZertoPublic/ZertoApiWrapper/issues/47) covers additional details.
-* A new function has been added; `Invoke-ZertoEvacuateVra`. This function will allow users to evacuate a target VRA by specifying a Host Name, VRA Name, or VRA Identifier. All VMs currently replicating to the specified location will be migrated to different targets. [Issue 51](https://github.com/ZertoPublic/ZertoApiWrapper/issues/51)
-* A function has been added; `Copy-ZertoVpg`. This function will allow users to copy the settings of a single VPG and add new VMs to it. There is currently no customization beyond specifying the VMs to be placed in the newly created VPG. Should additional edits \ updates be required, they should be done post creation. [Issue 54](https://github.com/ZertoPublic/ZertoApiWrapper/issues/54)
-* Fixed [issue 57](https://github.com/ZertoPublic/ZertoApiWrapper/issues/57) where a `Start-ZertoFailoverTest` would throw an error complaining about validating the body parameter. This has been fixed and tested against Zerto Virtual Manager 7.5 Update 1 with Windows PowerShell 5.1 and PowerShell Core 6.2.
+* Addressed a reported [issue](https://github.com/ZertoPublic/ZertoApiWrapper/issues/60) in the `Get-ZertoRecoveryReport` function where the `-VpgIdentifier` parameter was not working. This parameter is not accepted by the API as a valid filter and is ignored. This parameter has been removed from the function.

ZertoApiWrapper/Public/Get-ZertoRecoveryReport.ps1

@@ -26,12 +26,6 @@ function Get-ZertoRecoveryReport {
         )]
         [ValidateNotNullOrEmpty()]
         [string]$pageSize,
-        [Parameter(
-            ParameterSetName = "filter",
-            HelpMessage = "The internal identifier of the VPG. You can specify more than one VPG, separated by commas."
-        )]
-        [ValidateNotNullOrEmpty()]
-        [string]$vpgIdentifier,
         [Parameter(
             ParameterSetName = "filter",
             HelpMessage = "The name of the VPG. You can specify more than one VPG, separated by commas."

docs/Get-ZertoRecoveryReport.md

@@ -142,22 +142,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -vpgIdentifier
-The internal identifier of the VPG.
-You can specify more than one VPG, separated by commas.
-
-```yaml
-Type: String
-Parameter Sets: filter
-Aliases:
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -vpgName
 The name of the VPG.
 You can specify more than one VPG, separated by commas.