-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get-RscType -InitialProperties fails to init more than one nested property #112
Comments
evcheng-rubrik
added a commit
that referenced
this issue
Jun 25, 2024
New Features: - Get-RscWorkload cmdlet - Retrieves information about any supported workload type, with various filtering capabilities. - Get-RscVmwareVm - Added -Relic switch. Use -Relic:$false to filter out Relics. -Relic will return only Relics. No usage of -Relic will return all (default operation). -Name parameter is now position 0, so you don't have to specify -Name. - Get-RscNutanixVm - New cmdlet to get Nutanix VMs - Register-RscRubrikBackupService - New cmdlet to register RBS on VMs - Get-RscRole - Gets list of RSC Roles - Get-RscPermission - Gets list of RSC Permissions from Role - New-RscPermission - Creates new RSC Permission object - Merge-RscPermission - Merges an RSC Permission object into a Role object - Set-RscRole - Updates a Role in RSC with a Role object - New-RscSla - Now accepts -DailySchedule as a parameter Fixes: - Issue [#112](#112) Breaking Changes: - Removed legacy Get-RscVsphereVm CS cmdlet. Please use Get-RscVmwareVm.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
When using
Get-RscType
to initialize properties of an object, if multiple nested properties are requested for a nested type, only the first property of the nested property tree is initialized. Subsequent properties return a null reference exception.Steps to Reproduce
Initialize properties with a single nested property:
Output:
Initialize properties with another single nested property:
Output:
Initialize properties with multiple nested properties:
Output:
Expected Behavior
Both
vsphereVirtualDisks.nodes.FileName
andvsphereVirtualDisks.nodes.Fid
should be initialized without causing a null reference exception.Actual Behavior
Only the first property (
FileName
orFid
) is initialized, and attempting to initialize multiple nested properties results in a null reference exception.The text was updated successfully, but these errors were encountered: