Comment 8 for bug 1634847

We can refresh the local controller info when other API calls are made.
But there can be no guarantee that the list-controllers information won't ever be out of date unless list-controllers also makes API calls to each controller, which we were avoiding. Hence there will always be a need for a --refresh argument if we accept that approach. show-controller etc can pull down the info required and update the local controllers file, but bear in mind it will be for that one controller only, not all of them. If we make list-controllers make an API call to each controller, and it blocks, how long to we wait? 0.5 seconds? 1 second? 10 seconds? We wanted to avoid all that and provided an explicit refresh. If the user really wants list-controllers to refresh, despite the limitations, could an alias be used?