Currently if someone use the config file to run Invoke-SCuBA the parameters will bypass the initial validation sets of the parameters at the top of Invoke-SCuBA
To reproduce
Add a parameter that you know will error out to scubaconfig.yamlInvoke-SCuBA -ConfigFilePath scubaconfig.yaml
Observe the error message.
Expected behavior
For ScubaGear, to validate the parameters passed into the config file on read rather than being enforced down the line.
Any helpful log output or screenshots
Example passing in an invalid -ProductNames within the config file.
The error is caught down the line at Invoke-Connection
🐛 Summary
Currently if someone use the config file to run Invoke-SCuBA the parameters will bypass the initial validation sets of the parameters at the top of
Invoke-SCuBA
To reproduce
Add a parameter that you know will error out to
scubaconfig.yaml
Invoke-SCuBA -ConfigFilePath scubaconfig.yaml
Observe the error message.
Expected behavior
For ScubaGear, to validate the parameters passed into the config file on read rather than being enforced down the line.
Any helpful log output or screenshots
Example passing in an invalid
-ProductNames
within the config file. The error is caught down the line atInvoke-Connection