Fixed status output to use auth information from AuthManager #6529
+78
−22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses #6360. The root problem is that the TUI was directly loading the
auth.jsonfile to access the auth information. It should instead be using the AuthManager, which records the current auth information. Theauth.jsonfile can be overwritten at any time by other instances of the CLI or extension, so its information can be out of sync with the current instance. The/statuscommand should always report the auth information associated with the current instance.An alternative fix for this bug was submitted by @chojs23 in this PR. That approach was only a partial fix.