-
Notifications
You must be signed in to change notification settings - Fork 197
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
--sdk-auth has been depricated #220
Comments
FWIW the documentation change could be something like this::
|
This issue is idle because it has been open for 14 days with no activity. |
This issue is idle because it has been open for 14 days with no activity. |
@petetnt are you facing any issues with the steps mentioned here: https://github.com/Azure/login#configure-a-service-principal-with-a-secret? |
Hi @shpraka, configuring a service principal with a secret does work, but still it complains about
This is just painful for the end users, I think the real solution would be to unify these with the whole Azure ecosystem 🤷 |
@petetnt I understand and agree with the pain you're facing. Since we are dependent on Azure/login, we will have to wait if they share some new instructions for the same. |
@petetnt I am closing this issue for now feel free to re-open or create new one in case you ran into any issues. |
Similar to Azure/github#152, the
--sdk-auth
parameter recommended in the README has been deprecated. Root issue is at Azure/azure-cli#20743See https://github.com/Azure/webapps-deploy#configure-deployment-credentials-1 on how it's used.
There should be new instructions how to translate the values output by the command without the flag to ones needed by
@azure/webapps-deploy
, or there should be a new version of@azure/webapps-deploy
published that usesappId
,name
andpassword
instead.The text was updated successfully, but these errors were encountered: