influx config
This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.
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 command displays the active InfluxDB connection configuration
and manages multiple connection configurations stored, by default, in ~/.influxdbv2/configs.
Each connection includes a URL, token, associated organization, and active setting.
InfluxDB reads the token from the active connection configuration, so you don’t
have to manually enter a token to log into InfluxDB.
Usage
influx config [flags]
influx config [command]
influx config <config-name>Quickly switch between configurations
# Syntax
influx config <config-name>
# Example
influx config local-configTo quickly switch back to the previous configuration, use the following command:
influx config -Examples
# Show the active connection configuration
influx config
# Set a connection configuration as active
influx config local-configSubcommands
| Subcommand | Description |
|---|---|
| create | Create a connection configuration |
| list | List connection configurations |
| delete | Delete a connection configuration |
| set | Set or update a connection configuration |
Flags
| Flag | Description | |
|---|---|---|
-h | --help | Help for the config command |
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.