influxdata / influxdata/influxdb
Influxdb 2.1.1 v1 auth create only uses the last Bucket of stringArray
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
I am using influx 2.1 on Docker and trying to create a v1 user for access multiple Buckets but only the last one in an read oder write array is used. The first one(s) are ignored.
```
# influxd version
InfluxDB 2.1.1 (git: 657e1839de) build_date: 2021-11-09T03:03:48Z
# influx v1 auth create --read-bucket 0163a2bad970198b --write-bucket b12eadad7ed49a1f --read-bucket b12eadad7ed49a1f --write-bucket 0163a2bad970198b --username example
# influx v1 auth list
ID Description Username v2 User Name v2 User ID Permissions
08eefba1b1e17000 example admin 08d5468d88a48000 [read:orgs/23b79a7c9985f81a/buckets/b12eadad7ed49a1f read:orgs/23b79a7c9985f81a/buckets/b12eadad7ed49a1f write:orgs/23b79a7c9985f81a/buckets/0163a2bad970198b write:orgs/23b79a7c9985f81a/buckets/0163a2bad970198b]
```
Contributor guide
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 the `influx v1 auth create` command against InfluxDB 2.1.1 in Docker, then trace the v1 auth create handling for repeated `--read-bucket` and `--write-bucket` arguments. Done means the created authorization lists every specified read and write bucket rather than only the last one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100