influx export stack
The influx export stack command exports all resources associated with a stack as a template.
All metadata.name fields remain the same.
To export resources as a template, you must use the Operator token created for the initial InfluxDB user or an All-Access token. For information about creating an All-Access token, see Create an authentication token.
Usage
influx export stack <stack_id> [flags]
Flags
| Flag | Description | Input Type | Maps to ? | |
|---|---|---|---|---|
-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 | --file | Template output file. Defaults to stdout. Use .yml or .json file extensions. | string | |
-h | --help | Help for the export stack command | ||
--host | HTTP address of InfluxDB (default http://localhost:8086) | string | INFLUX_HOST | |
-o | --org | Organization name that owns the resources (mutually exclusive with --org-id) | string | INFLUX_ORG |
--org-id | Organization ID that owns the resources (mutually exclusive with --org) | string | INFLUX_ORG_ID | |
--skip-verify | Skip TLS certificate verification | |||
-t | --token | Authentication token | string | INFLUX_TOKEN |
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.
Export a stack as a template
influx export stack $STACK_ID
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, the following resources are available:
InfluxDB Cloud and InfluxDB Enterprise customers can contact InfluxData Support.