windowsgitazuremicrosoft-documentation

git on Azure don't ask me for password, push fails


I am learning Azure, and what I observed, a huge part of the official Microsoft documentation is either obsolete, or doesn't correspond to the reality, or just does not work as expected because of errors.

One example is the article I study, Create deployment slots (on Azure).

Here I am stuck with the following:

enter image description here

The first question is, what the hell is the "Cloud Shell", I didn't find such a thing in the Azure portal, so I supposed they talk about the Console from the Development Tools section... OK, lets go :

D:\home\demoapp\app-service-web-dotnet-get-started>git remote add production https://myusername@mytestslots.scm.azurewebsites.net:443/MyTestSlots.git

D:\home\demoapp\app-service-web-dotnet-get-started>git push production
Logon failed, use ctrl+c to cancel basic credential prompt.
fatal: could not read Password for 'https://myusername@mytestslots.scm.azurewebsites.net:443': Bad file descriptor

So, OK, I am not asked for password!?! What to do?

I tried

git config --global core.askpass /usr/libexec/git-core/git-gui--askpass

but

error: cannot spawn /usr/libexec/git-core/git-gui--askpass: No such file or directory

tried

git config --global core.askpass "C:\Program Files\Git\\mingw64\libexec\git-core\git-gui--askpass"

but the same

error: cannot spawn C:\Program Files\Git\mingw64\libexec\git-core\git-gui--askpass: No such file or directory

Please help.


Solution

  • To answer your question about Cloud Shell in Azure Portal, please see this link: https://learn.microsoft.com/en-us/azure/cloud-shell/quickstart.

    Regarding your comments about the quality of the content on Microsoft Learn, you can provide feedback by navigating to the bottom of the page (https://learn.microsoft.com/en-us/learn/modules/stage-deploy-app-service-deployment-slots/3-exercise-create-deployment-slots) and then clicking on reporting an issue. This will redirect you to this link.

    You can provide detailed feedback there. In my experience, Microsoft folks are quite responsive to the feedback.