On ArgoCD 3.1.0 enabling Azure Workload Identity for an existing ArgoCD Application doesn't work? Only new apps appear to work

[pearj]

Hi,

I'm using Azure Devops for our Git Repos with ArgoCD 3.1.0, and I'm trying to transition from PAT tokens to Azure Workload Identity, however I don't seem to be able to enable workload identity for existing ArgoCD Applications. It seems to remember the old settings somehow.

I've tried the following:

• Manually updating the repo k8s secret removing username/password and adding useAzureWorkloadIdentity: "true" to the secret, but I just get authentication failures.
• Adding a new repository url that uses a different domain (as azure devops gives you two options dev.azure.com and yourorg.visualstudio.com), then updating the ArgoCD Application to use the new repository. However, I still authentication errors that reference the old repository url.

If I instead create a brand new ArgoCD app that references a repository that has workload identity enabled, then that actually seems to be working fine.

What causes the repo url not to switch over to workload identity properly?

[pearj]

Oh it looks like it might be this #23478