Add --no-cache to not use the cache and force a refresh

[Gavin89]

Output of aws-sso version:

Example output:
❯ aws-sso version
AWS SSO CLI Version 1.13.1 -- Copyright 2021-2023 Aaron Turner
7c08e58ad2a2c941bfa42ad98b0429f3fefa1ca7 (v1.13.1) built at 2023-08-28T23:03:47+0000

Describe the bug:
We have a unique scenario where we are creating/deleting many accounts, it appears that when we run aws-sso list it appears to be returning / caching old accounts that have been deleted, and it doesn't appear to be showing any new accounts. Using this tool https://github.com/benkehoe/aws-sso-util I can see the new accounts, and also it does not return old accounts.

To Reproduce:

1. aws-sso list

As this has our accounts info, I can't copy and paste, but for context I have around 40 AWS accounts with 2 roles each that are active, maybe there is a limitation on how many you bring back, or maybe you cache accounts when bringing them back instead of doing api call every time

An example is in my AWS SSO I can see tmp-gh109 but when I run aws-sso list, it does not appear in the list. However, running aws-sso-util roles I can see that account.

I can also see tmp-gh108 which has been deleted from AWS SSO and does not show in aws-sso-util but shows in aws-sso list

[synfinatic]

Not a bug, but more of as-designed. If you have many accounts it can take a few dozen (or more) seconds for AWS to return all the results due to rate limiting. Even a few accounts can add noticeable lag to many aws-sso commands.

Anyways, this is all documented in the docs, so I encourage you to read them. That said, this question (or versions of it) seems to be coming up enough that I should see about adding a --no-cache option or something along the lines to force a cache refresh.

[Gavin89]

How come aws-sso-util seems to handle many accounts thought?

[synfinatic]

Because aws-sso-util has fewer features and can rely solely on the ~/.aws/config file for its "cache". Any time it needs to update the ~/.aws/config file it takes the same hit.

[Gavin89]

How come it is bringing back new active accounts though? like even running aws-sso list now it still does not show my tmp-gh109 so im unable to access this acc

[synfinatic]

Sorry, not sure I understand what you're saying. Can you rephrase and perhaps provide more details? Are you suggesting you found a bug?

[Gavin89]

Hi, so I have created a new AWS Account called tmp-gh109 but when I run aws-sso list this does not appear in the list. I would expect to see it.

I can see the new account in my AWS SSO Okta, so I know it is there. Running the below with the account ID I also get

❯ aws-sso exec -A <redacted> -R AdministratorAccess
WARNING Unable to update cache                        error="invalid AWS AccountID: <redacted>"
ERROR   Unable to find role in cache.  Unable to set AWS_SSO_PROFILE 

So it is like the tool is not pulling latest from AWS SSO, or it has cached so there for not doing an API call, or there is some sort of bug.

[synfinatic]

https://github.com/synfinatic/aws-sso-cli/blob/main/docs/config.md#sso-cache-options
https://github.com/synfinatic/aws-sso-cli/blob/main/docs/commands.md#cache