influxdata / influxdata/influx-cli
`influx v1 auth ls` fails with `unable to decode response content type "text/html"`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 75
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Context: I'm following https://docs.influxdata.com/influxdb/cloud/tools/grafana/?t=InfluxQL in order to be able to query InfluxDB from Grafana using InfluxQL instead of Flux. My InfluxDB is an [InfluxDB Cloud Free Plan](https://www.influxdata.com/influxdb-cloud-pricing/)
### Steps to reproduce
I did
```
$ influx v1 dbrp create --db 030solutions --rp 030solutions --bucket-id a46c7dcec28c0316 --default
```
but then I can't create a v1 user/password as any command involving `influx v1 auth` fails with:
```
$ influx v1 auth ls
Error: could not find Authorizations for specified arguments: unable to decode response content type "text/html"
```
### Version
`influx` binary downloaded from https://dl.influxdata.com/influxdb/releases/influxdb2-client-2.7.1-linux-amd64.tar.gz running on Ubuntu 22.04
### Additional info
```
$ influx version
Influx CLI dev (git: none) build_date: 2023-04-05T17:15:07Z
$ influx bucket ls
ID Name Retention Shard group duration Organization ID Schema Type
0dbbb9df499fe0dc _monitoring 168h0m0s n/a d9a6d519ad91c068 implicit
2905109a0d9e4d8b _tasks 72h0m0s n/a d9a6d519ad91c068 implicit
a46c7dcec28c0316 processing_pipeline 720h0m0s n/a d9a6d519ad91c068 implicit
$ influx v1 dbrp ls
ID Database Bucket ID Retention Policy Default Organization ID
0b017fc7da9fd000 030solutions a46c7dcec28c0316 030solutions true d9a6d519ad91c068
VIRTUAL DBRP MAPPINGS (READ-ONLY)
----------------------------------
ID Database Bucket ID Retention Policy Default Organization ID
```
// CC @nikste
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing `influx v1 auth ls` against the stated InfluxDB Cloud Free Plan and tracing the v1 auth command's response handling. Determine why the command receives `text/html` and identify a testable correction; done means the command lists authorizations or reports a clear, appropriate error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100