DeployToTenatns: When we have a non-existing tenant name (in my case due to spelling mistake where I wrote say "customr" instead of "customer"), we do not get any warnings or error. Moreover the console log from "Deploy-App.ps1" script was misleading like this:
Publishing Customer (C:\Users\PIPELI~1.SER\AppData\Local\Temp\58f39d55-f49d-4616-a81f-9b45d47c0eea) to customr
Removing unused app v19.0.30.0
Publishing v19.0.31.0
Investigating app Customer v19.0.31.0 installed=False
Checking installation status for app Customer 19.0.31.0
No. of newer apps: 0
Installed: False
Finishing: Deploy to Environment
But in reality no app got removed or published. Ideally it should give an error when the tenant is not available/accessible
DeployToTenatns: When we have a non-existing tenant name (in my case due to spelling mistake where I wrote say "customr" instead of "customer"), we do not get any warnings or error. Moreover the console log from "Deploy-App.ps1" script was misleading like this:
Publishing Customer (C:\Users\PIPELI~1.SER\AppData\Local\Temp\58f39d55-f49d-4616-a81f-9b45d47c0eea) to customr
Removing unused app v19.0.30.0
Publishing v19.0.31.0
Investigating app Customer v19.0.31.0 installed=False
Checking installation status for app Customer 19.0.31.0
No. of newer apps: 0
Installed: False
Finishing: Deploy to Environment
But in reality no app got removed or published. Ideally it should give an error when the tenant is not available/accessible