You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Both vsphereVirtualDisks.nodes.FileName and vsphereVirtualDisks.nodes.Fid should be initialized without causing a null reference exception.
Actual Behavior
Only the first property (FileName or Fid) 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:
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.
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: