Incorrect error with `axiom dataset list` for bad deployment alias
- Dominant language
- Go
- Stars
- 60
- Forks
- 11
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 10
Description
When using an alias to that is no longer valid the `axiom dataset list`
command returns an error of the form:
```bash
$ AXIOM_DEPLOYMENT=bogus-no-longer-valid-env axiom dataset list
Error: cannot decode response with unknown content type
```
This can be cross-checked with `axiom auth status` which will show valid and non-valid auth tokens by alias
Contributor guide
Research direction
Reproduce the problem with AXIOM_DEPLOYMENT=bogus-no-longer-valid-env axiom dataset list, then compare its response handling with axiom auth status for the same alias. Trace the dataset list command's handling of an invalid deployment response; done means the command reports a useful invalid-alias or authentication error instead of "cannot decode response with unknown content type."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100