Documentation

influx secret update

The influx secret update command adds and updates secrets. Provide the secret key with the -k or --key flag. You may also provide the secret value with the -v or --value flag. If you do not provide the secret value with the -v or --value flag, enter the value when prompted.

Providing a secret value with the -v or --value flag may expose the secret in your command history.

Usage

influx secret update [flags]

Flags

FlagDescriptionInput typeMaps to ?
-c--active-configCLI configuration to use for commandstring
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-h--helpHelp for the update command
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
--hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
-k--key(Required) Secret keystring
-o--orgOrganization name (mutually exclusive with --org-id)stringINFLUX_ORG
--org-idOrganization ID (mutually exclusive with --org)stringINFLUX_ORG_ID
--skip-verifySkip TLS certificate verification
-t--tokenAuthentication tokenstringINFLUX_TOKEN
-v--value(Required) Secret valuestring

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by the active influx CLI configuration. If you do not have a CLI configuration set up, use the appropriate flags to provide these required credentials.

Add a secret
influx secret update \
  --key EXAMPLE_KEY \
  --value EXAMPLE_VALUE
Update an existing secret
influx secret update \
  --key EXAMPLE_KEY \
  --value NEW_EXAMPLE_VALUE

Cloud or OSS?

InfluxDB OSS 2.0 now generally available!

InfluxDB OSS 2.0 is now generally available and ready for production use. See the InfluxDB OSS 2.0 release notes.

For information about upgrading to InfluxDB OSS 2.0, see: