I realize the documentation states that the section "CustomRequirementRule" will be further documented in the future, but I went ahead and defined the required variables in a app.json file as this was desired in my particular case for Dell Command | Update. (My custom requrement rule variables and values where based off of the expected variables in the switch statement starting on line 350 of New-Win32App.ps1)
When New-Win32App.ps1 is running and has app.json has custom requirement rule script files defined, the pipeline will fail because the script file is missing in the Scripts folder. After investigating this my conclusion is that the Prepare-AppPackageFolder.ps1 should process each custom requirement rule with script files while processing "app.json" (line 110) in the switch statement.
Adding the following to line 110 in Prepare-AppPackageFolder.ps1 did the trick for me:
I realize the documentation states that the section "CustomRequirementRule" will be further documented in the future, but I went ahead and defined the required variables in a app.json file as this was desired in my particular case for Dell Command | Update. (My custom requrement rule variables and values where based off of the expected variables in the switch statement starting on line 350 of New-Win32App.ps1)
When New-Win32App.ps1 is running and has app.json has custom requirement rule script files defined, the pipeline will fail because the script file is missing in the Scripts folder. After investigating this my conclusion is that the Prepare-AppPackageFolder.ps1 should process each custom requirement rule with script files while processing "app.json" (line 110) in the switch statement.
Adding the following to line 110 in Prepare-AppPackageFolder.ps1 did the trick for me: