Closed domingosbarreto closed 1 year ago
Nevermind, the enableTaskScheduler is a switch... Resolved by changing to this:
...
-appBuild $appBuild -appRevision $appRevision `
-enableTaskScheduler `
-NewBcContainer { Param([Hashtable]$parameters)
...
Describe the issue When using Run-AlPipeline, when overriding the NewBcContainer parameter to add a call to UploadImportAndApply-ConfigPackageInBcContainer this runs correctly but then a new tenant named "True" is created. The intention is to use always the default tenant.
I don't know and cannot find where this is being triggered, an this causes the failure when installing apps that requires the data previously imported with UploadImportAndApply-ConfigPackageInBcContainer (that is imported to the default tenant) and the installation is being preformed on the newly created tenant (named True).
Scripts used to create container and cause the issue
Full output of scripts