fix(api): Fix panic that occurred when sentry-cli login
called with --auth-token
#1893
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 fixes the bug in #1885 that led us to revert that commit. The bug, reported in #1888, caused the CLI to panic when the
sentry-cli login
command was called with the--auth-token
argument.We determined that the CLI panicked because the
auth_token
was being downcast to aString
instead of to anAuthToken
type when being read from thematches
within thelogin
command. This PR corrects thelogin
command, so that theauth_token
is correctly obtained from thematches
as anAuthToken
. We also checked whether theauth_token
argument was being read as aString
anywhere else in the code, and found that thelogin
command was the only place the argument was being read as aString
. Therefore, we would expect this PR to fix this class of bug completely.Fixes GH-1859
Fixes GH-1888