Open nije-MSFT opened 9 months ago
Is there a specific reason you are using Azure Account version 0.9.11? Our latest versions of the resource extensions no longer use the Azure Account extension. Please update to the latest versions.
That's all that's been approved for SAW usage for our org. I've put in a request to have the latest versions reviewed, but it could take a month or more for the review to complete.
That's all that's been approved for SAW usage for our org. I've put in a request to have the latest versions reviewed, but it could take a month or more for the review to complete.
Wow, ok. Well 0.9.11 is from November 2021, and version 1.85.1 of VS Code is from November 2023. It's very likely that the old version of the Azure Account extension is not compatible with this relatively new version of VS Code. One thing you could try is installing an older version of VS Code (if that's possible 😄).
Also, what extension are you hoping to use alongside the Azure Account extension?
I already looked into VS Code downgrades and that doesn't seem to be possible. I think older versions of software get revoked after a while. It sounds like I'm just sort of stuck while I wait for the new version review. I suppose I could look into where kubeconfig is located and just add tokens manually to try and unblock my team.
My team does a lot with AKS and we're trying to get our AKS workflows migrated over from our normal dev machines. The account extension makes hopping between a bunch of different clusters and subscriptions really easy.
Does your account belong to more than one directory? No
Any other information about your Azure account that may be useful:
I get the Azure login browser page but then an error pops up in VS Code saying The 'emitter' argument must be an instance of EventEmitter or EventTarget. Received an instance of AbortSignal
Happy to jump on a debugging session if needed