New-RubrikReport does not allow use of all templates

[railroadmanuk]

Current Behavior:

Create report using ObjectProtectionSummary template:

PS /mnt/c/WINDOWS/System32> $report = new-rubrikreport -Name $ReportName -ReportTemplate 'ObjectProtectionSummary' -Verbose
New-RubrikReport: Cannot validate argument on parameter 'ReportTemplate'. The argument "ObjectProtectionSummary" does not belong to the set "ProtectionTasksDetails,ProtectionTasksSummary,SystemCapacity,SlaComplianceSummary" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again.

Expected Behavior:

Can use any of the available templates. In 5.1 this is the list:

Steps to Reproduce:

See above.

Context:

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Rubrik PowerShell Module Version: 5.0.1
• PowerShell Version: 7.0.0
• Operating System: WSL 2 / Ubuntu 20.04

[jaapbrasser]

I added additional reports to the valideset, how does this look @railroadmanuk ?

[railroadmanuk]

Thanks for fixing this chaps, the list of available templates is CDM version dependent, not sure if you want to take that into account or just let it throw in older CDM versions...

…

On Wed, 27 May 2020 at 14:55, Mike Preston ***@***.***> wrote: Closed #628 <#628> via #629 <#629>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#628 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACF6LPNQYEZMA4ZWLMZI4ULRTULVHANCNFSM4ND2LQCQ> .

-- [image: RubrikLogo140x401574358943.png] <https://www.rubrik.com/> *Tim Hynes* DevOps Sales Engineer at Rubrik *E *[email protected] *M *+44 7565 876580 *W*www.rubrik.com

[jaapbrasser]

I would opt for just letting it throw, as the alternative is to create a dynamic parameter based on the API version and dynamic parameters are a bit of a pain in PowerShell. I think it should be clear enough when it fails because an unsupported report is requested on a older CDM version.

Good feedback though!