We have quite a few cases where we do not have a classic parameters.json file and the test script fails because it 'by default' expects one. One example is the 'virtualMachines' module:
I'd highly recommend to avoid any assumptions of the parameter file and instead optionally offer to either provide an array of parameter file paths, or an array of parameter file names (assuming that the files are in a .parameters folder). This also allows us to get rid of the DeployAllModuleParameterFiles parameter.
The parameter should in general be optional, as it is not needed for the pester tests
We have quite a few cases where we do not have a classic
parameters.jsonfile and the test script fails because it 'by default' expects one. One example is the 'virtualMachines' module:I'd highly recommend to avoid any assumptions of the parameter file and instead optionally offer to either provide an array of parameter file paths, or an array of parameter file names (assuming that the files are in a
.parametersfolder). This also allows us to get rid of theDeployAllModuleParameterFilesparameter.The parameter should in general be optional, as it is not needed for the pester tests