Skip to content

Latest commit

 

History

History
18 lines (18 loc) · 2.19 KB

todo.md

File metadata and controls

18 lines (18 loc) · 2.19 KB

ToDo items for DRSRule module

  • look into possibility of increasing speed in Get-DrsVMGroup (somewhat slow in medium to large environments)
  • investigate possiblity of removing all VM/VMHost members of DRS VM/VMHost groups. UI does not support, but API docs say that the member field can have zero or more values
  • add Pester tests
    • New-Drs*, Set-Drs*, Remove-Drs* tests
  • add SDRS rule support
  • add ability to specify prefix for names of new objects during Import
  • add support for [string[]] values to -Name param for Get-DrsVMGroup, Get-DrsVMHostGroup
  • add -Type param for Import-DrsRule, so one can import just rules/groups of given type
  • add verbosity to WhatIf info for
    • New/Set-DrsVMHostGroup output -- include VMHosts' names
    • New/Set-DrsVMGroup output -- include VMs' names
  • add ability to rename groups/rules via Set-Drs* functions
  • ?remove spots that re-assign values to param vars (use new var name instead of re-using param name, like $VM = $VM | %{...do something...}); there is slight weirdness when acting on those further: ValidateScript() seems to run again, and if the var is not of the given type, throws The variable cannot be validated because the value System.Management.Automation.PSObject[] is not a valid value for the VMHost variable., for example, but later on in the function, not at the start
  • update Get-Drs* behavior to match standard Get-* cmdlets' behavior of returning error when no item found of given name when $Name has no wildcard:
    • Get-DrsVMGroup bogusGroupName should throw error
  • add function to get objects from exported JSON, to essentially return info items that could be used for New-Drs*, but that would be useful to see what items are stored in given JSON
  • maybe (if only for the sake of thoroughness): look into addressing potential issues that might arise from Compare-Object calls where a reference- or difference object might be $null (which would cause Compare-Object to throw an error) -- an example of where this was fixed: Set-DrsVMGroup; may be minimal chance of hitting bug, as DRS VM/VMHost groups should generally have members, but may be worth a look throughout rest of code