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
{{ message }}
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
This file should accept an Object as a parameter, and use that to build *.Vester.ps1 files. This will allow users to quickly build test files for new settings. There of course is an assumption that each item in the object could be gathered and fixed in the same way.
Current Behavior
Currently users need to manually create the test files.
Possible Solution
I'll check in my first pass. I think that a parameter for "command" will need to be added, as the current solution is hardcoded with "Get-AdvancedSetting -Entity ......". Also, better handling of special characters being returned by PowerCLI in the setting names.
Steps to Reproduce (for bugs)
n/a
Context
This quick script allowed me to create a list of 600+ advanced settings for vCenter in seconds. I think for some users thats too much, and they may not care about all of those. But it's a nice feature to have available if you need to compare every detail about two separate Items in your environment.
Your Environment
Vester module version used: 1.2.0
PowerCLI version: 6.5.2.6
Pester version: 4.0.5
Operating System and PowerShell version: Win10, PS5 build 15063, Rev 608
The text was updated successfully, but these errors were encountered:
jpsider
added a commit
to jpsider/Vester
that referenced
this issue
Sep 24, 2017
Expected Behavior
This file should accept an Object as a parameter, and use that to build *.Vester.ps1 files. This will allow users to quickly build test files for new settings. There of course is an assumption that each item in the object could be gathered and fixed in the same way.
Current Behavior
Currently users need to manually create the test files.
Possible Solution
I'll check in my first pass. I think that a parameter for "command" will need to be added, as the current solution is hardcoded with "Get-AdvancedSetting -Entity ......". Also, better handling of special characters being returned by PowerCLI in the setting names.
Steps to Reproduce (for bugs)
n/a
Context
This quick script allowed me to create a list of 600+ advanced settings for vCenter in seconds. I think for some users thats too much, and they may not care about all of those. But it's a nice feature to have available if you need to compare every detail about two separate Items in your environment.
Your Environment
The text was updated successfully, but these errors were encountered: