influx config set

  • influx CLI 2.0.0+
  • InfluxDB 2.0.0+
  • Updated in CLI 2.5.0

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

The influx config set command updates information in an InfluxDB connection configuration in the configs file (by default, stored at ~/.influxdbv2/configs).

Usage

influx config set [flags]

Command aliases

set , update

Flags

FlagDescriptionInput typeMaps to ?
-a--activeSet the specified connection to active
-n--config-nameName for the InfluxDB connection configuration to set or updatestring
-h--helpHelp for the set command
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
-u--host-urlURL for InfluxDB connection configuration to set or updatestring
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
-o--orgOrganization name for the connection configurationstring
-t--tokenAPI tokenstringINFLUX_TOKEN
-p--username-password(OSS only) Username (and optionally password) to use for authentication.
Include username:password to ensure a session is automatically authenticated. Include username (without password) to prompt for a password before creating the session.		string

Examples

Update a connection configuration and set it to active
influx config set --active \
  -n config-name \
  -t mySuP3rS3cr3tT0keN \
  -o example-org
Update a connection configuration and do not set it to active
influx config set \
  -n config-name \
  -t mySuP3rS3cr3tT0keN \
  -o example-org

Was this page helpful?

Thank you for your feedback!