JUST BROKEN: Method to extract name and role of AWS account to choose correct container is broken just now!
scastria opened this issue · 6 comments
AWS must have just changed the format/content of how they handle SSO connections as your plugin (which I rely on EVERY DAY) now gets confused as to which AWS account is being connected to. The name of the container chosen is now, the literal string "name" instead of the actual name of the AWS account. Therefore, no matter which account I click on, I get the same container named "name" as my container. This, of course, means I cannot open more than 1 AWS account at a time which breaks the point of this plugin. Please fix right away. I can donate money if needed.
Hmm.. I was just playing with the container name template preference in this plugin which I had customized to just be "name" and deleted it completely. I then restarted the browser and the default "name role" template was restored AND it did properly name the container. I then changed the name template back to "name" and restarted my browser and then everything was working again. Not sure what happened. Will close this ticket.
AWS must have just changed the format/content of how they handle SSO connections as your plugin (which I rely on EVERY DAY) now gets confused as to which AWS account is being connected to. The name of the container chosen is now, the literal string "name" instead of the actual name of the AWS account. Therefore, no matter which account I click on, I get the same container named "name" as my container. This, of course, means I cannot open more than 1 AWS account at a time which breaks the point of this plugin. Please fix right away. I can donate money if needed.
I have exactly the same issue, check this link:
#12 (comment)
I'll try to follow your steps to fix this tomorrow. Thanks bro!
Had the same issue and this fixed it for me too. Just remember to restart your browser after saving the container name template.
Thanks @scastria !
Hm, then I have no idea. It might be worth doing uninstalling and reinstalling the extension, to try and "refresh" the way it is dealing with name
.