Open
Description
Expected behavior:
Update an existing v1 auth token to add / remove read / write access to a bucket
Actual behavior:
The influx v1 auth
currently allows us to only create and delete v1 auth tokens. Thus after the creation of a v1 auth token, if we create a new bucket and want to make sure that the v1 auth token has read / write access to this bucket, we have to delete the existing v1 auth token and recreate it. Creating a separate auth token is not something I want to do.
Environment info:
- System info:
uname -srm
Linux 4.15.0-117-generic x86_64
- InfluxDB version:
influxd version
InfluxDB 2.0.2 (git: 84496e507a) build_date: 2020-11-19T03:59:35Z
Console output:
root@influxdb-service-0:/# influx v1 auth -h
Authorization management commands for v1 APIs
Usage:
influx v1 auth [flags]
influx v1 auth [command]
Aliases:
auth, authorization
Available Commands:
create Create authorization
delete Delete authorization
list List authorizations
set-active Change the status of an authorization to active
set-inactive Change the status of an authorization to inactive
set-password Set a password for an existing authorization
Flags:
-h, --help Help for the auth command
Use "influx v1 auth [command] --help" for more information about a command.