Documentation

Update secrets

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

Update secrets using the influx command line interface (CLI) or the InfluxDB API.

Update a secret using the influx CLI

Use the influx secret update command to update a secret in your organization. Provide the secret key to update 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.

# Syntax
influx secret update -k <secret-key>

# Example
influx secret update -k foo

Update a secret using the InfluxDB API

Use the PATCH request method and the InfluxDB /orgs/{orgID}/secrets API endpoint to update a secret in your organization.

Include the following:

  • Your organization ID in the request URL
  • Your API token in the Authorization header
  • The updated secret key-value pair in the request body
curl --request PATCH http://localhost:8086/api/v2/orgs/<org-id>/secrets \
  --header 'Authorization: Token YOURAUTHTOKEN' \
  --header 'Content-type: application/json' \
  --data '{
	"<secret-key>": "<secret-value>"
}'

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