Closed kesselschlaeger closed 3 years ago
The tasks has all the needed Powershell modules included and I just tried the deploy task myself and I didn't encounter any errors, so maybe you can recreate the task to see if the error disappears.
Hello @kesselschlaeger, did it work to you in the end? I'm getting this error for the first time after using this package many times in the past. I'm wondering if there are any problems with the RolloutEnvironment variable that is behind the scene but that we cannot set in the package thanks a lot
I am receiving this same error, but only when deploying using the Service Principle. Is there a workaround or a way we can setup this parameter in the deployment task?
Hi All,
Sorry for the ignorance on my side, but looking at this issue I misjudged it in the first place.
The only reference to RolloutEnvironment
is when it is extracted from the ServerName
parameter of the task. Is this set correctly, like asazure://westeurope.asazure.windows.net/fabrikam
?
-JP
Bingo! That was my issue, I had the incorrect server name. Once fixed everything deployed.
Thank you for this package!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hello,
we try to create a release pipeline for an AS Deployment. for authentication we use a service principal. in this case we get the error: Cannot bind argument to parameter 'RolloutEnvironment' because it is null. i think you use an older azure powershell library?
any ideas? Best regards André