influx stacks init

  • influx CLI 2.0.1+
  • InfluxDB 2.0.1+

The influx stacks init command initializes an InfluxDB stack.

Usage

  1. influx stacks init [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 init command
—hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
—hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
—http-debugInspect communication with InfluxDB servers.string
—jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
-o—orgOrganization name (mutually exclusive with —org-id)stringINFLUX_ORG
—org-idOrganization ID (mutually exclusive with —org)stringINFLUX_ORG_ID
—skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
-d—stack-descriptionStack descriptionstring
-n—stack-nameStack namestring
-u—template-urlTemplate URLs to associate with a stacklist of strings
-t—tokenAPI tokenstringINFLUX_TOKEN

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
Initialize a stack with a name and description
  1. influx stacks init -n "Example Stack" -d "InfluxDB stack for monitoring some awesome stuff"
Initialize a stack with a name and URLs to associate with the stack
  1. influx stacks init -n "Example Stack" -u https://example.com/template-1.yml

templates