-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: AzurePowerShellV4 Cannot read property 'retrieveSecret' of undefined #18364
Comments
This issue seems to be identical to issue: #18365 I'm also seeing that the previous version 4.221.103 was working, and since the update to 4.223.0 we're getting this issue. |
Having the same error here, seems like version 4.223.0 has this issue |
Same here - all my pipelines just stopped working today |
Running pipeline in debug mode gives the following information: App Service Application settings are already present. |
Same error here (on self hosted), reverting to |
Fixed with fixed version, but this is a workaround. Need to be able to subscribe to minor/revisions for security and if sdk changes.
|
Nice to know the workaround |
same error too, i noticed we had deployments working with 4.221.103 just before release, we dont use YAML so downgraded to version 3 seems to work ok for now as a workaround [using MS hosted] |
same issue here, ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined |
Similarly as in #18360 Thank you for the rollback! |
Duplicating with #18361 . |
Task name
Azure App Service deploy
Task version
4.223.0
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-2019
Task log
Relevant log output
2023-05-25T11:35:47.0636252Z ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined
Aditional info
Has worked flawlessly until today, when it stopped working all of a sudden.
The text was updated successfully, but these errors were encountered: