Documentation

influx config set

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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud Serverless