Skip to main content

Azure DevOps Server- Update Git credentials

Oh no, after writing a lot of posts about what I thought would be an easy operation, I'm back again with a last follow up post on moving an Azure DevOps Server instance from HTTP to HTTPS.

If you missed the previous posts:

In this last post(I really promise) I want to talk about Git Credential Manager.

Git Credential Manager simplifies authentication with your Azure Repos Git repositories. Credential managers let you use the same credentials that you use for the Azure DevOps Services web portal.

It can be installed as part of Git for Windows and thanks to it you don’t need use SSH keys or Personal Access Tokens to connect to your Azure DevOps Git repositories.

The problem was that after switching to HTTPS my Git credentials no longer seemed to work. Instead when I tried to do a git operation, it failed with the following error message:

$ git pull
fatal: Authentication failed for `repo url/`

To fix it I had to remove the existing credentials. Therefore I went  to Control Panel -> Credential Manager.

In the list of Generic Credentials I searched for the git repo credentials and clicked on Remove:

After that the authentication pop up reappeared and I could reenter my credentials.

    Popular posts from this blog

    .NET 8–Keyed/Named Services

    A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...