Documentation

influx stacks update

The influx stacks update command updates an InfluxDB stack.

Usage

influx stacks update [flags]

Flags

Flag Description Input type Maps to ?
--addResource Associate an existing resource with a stack string
-c --active-config CLI configuration to use for command string
--configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
-f --export-file Destination for exported template string
-h --help Help for the update command
--hide-headers Hide table headers (default false) INFLUX_HIDE_HEADERS
--host HTTP address of InfluxDB (default http://localhost:8086) string INFLUX_HOST
--http-debug Inspect communication with InfluxDB servers. string
-i --stack-id The stack ID to update string
--json Output data as JSON (default false) INFLUX_OUTPUT_JSON
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
-d --stack-description Stack description string
-n --stack-name Stack name string
-u --template-url Template URLs to associate with a stack list of strings
-t --token API token string INFLUX_TOKEN

Export an updated template

To prevent accidental changes, we strongly recommend exporting a new template any time you add additional resources to a stack using the --addResource flag with the influx stack update command. The updated stack will differ from the previous template. If you apply the outdated template, InfluxDB will revert the updates and remove the added resources.

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Update a stack with a name and description
influx stack update \
  -i ab12cd34ef56 \
  -n "New stack name" \
  -d "New stack description"
Update a stack with a name and URLs to associate with stack
influx stack update \
  -i ab12cd34ef56 \
  -n "New stack name" \
  --template-url https://example.com/template-1.yml \
  --template-url https://example.com/template-2.yml
Update a stack with new resources to manage
influx stacks update \
	--stack-id ab12cd34ef56 \
	--addResource=Bucket=12ab34cd56ef \
	--addResource=Dashboard=98zy76xw54vu
Update a stack with new resources and export the stack as a template
influx stacks update \
	--stack-id ab12cd34ef56 \
	--addResource=Bucket=12ab34cd56ef \
	--export-file /path/to/template-file.yml

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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 powered by TSM