Documentation

influx config set

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

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!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2