Pull Secret creation fails with Azure Container Registry when using az cli for login on Windows with docker "credsStore": "wincred"

[andrstor]

What happened? This is related to #2278. #2278 fixes the issue in most cases, but when you login to acr on windows using az acr login and your credentials are stored in .docker/config.json as such:

{
	"auths": {
		"test.azurecr.io": {}
	},
	"credsStore": "wincred"
}

No pullsecret is created by devspace and devspace outputs only:

pullsecret:test Ensuring image pull secret for registry: test.azurecr.io..

As using a credential manager is the default behaviour it is annoying.

Workaround is to force the config to not use the credential manager. E.g:

{
	"auths": {
		"helsenorge.azurecr.io": {
			"auth": "",
			"identitytoken": ""
		}
	}
}

What did you expect to happen instead? Devspace creates the pullsecret.

How can we reproduce the bug? (as minimally and precisely as possible) Do the same as in #2278, but makes sure your docker/config.json uses the credstore setup.

My devspace.yaml:

version: v2beta1
name: hn-configuration

...

pullSecrets:
  test:
    registry: test.azurecr.io
    secret: test-pull-secret

Local Environment:

• DevSpace Version: devspace version 6.1.1
• Operating System: windows
• ARCH of the OS: AMD64 Kubernetes Cluster:
• Kind
• Kubernetes Version: [use kubectl version] Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-02-16T12:38:05Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"windows/amd64"} Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0", GitCommit:"a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2", GitTreeState:"clean", BuildDate:"2022-09-01T23:30:43Z", GoVersion:"go1.19", Compiler:"gc", Platform:"linux/amd64"} Anything else we need to know?

/kind bug