Documentation

influx remote delete

Replication remotes and replication streams can only be configured for InfluxDB OSS.

The influx remote delete command delete an existing remote InfluxDB connection used for replication.

Usage

influx remote delete [command options] [arguments...]

Flags

FlagDescriptionInput typeMaps to ?
-i--idRemote connection ID to delete
--hostInfluxDB HTTP address (default http://localhost:8086)stringINFLUX_HOST
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-c--active-configCLI configuration to use for commandstring
--http-debugInspect communication with InfluxDB serversstring
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
-t--tokenInfluxDB API 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

Delete a remote

  1. Use influx remote list to get the ID for the remote you want to delete.
    $ influx remote list --org-id <OSS org ID> --token <OSS token>
    ID			        Name		Org ID
    0ooxX0xxXo0x 	    myremote    [...]
    
  2. Use the following command to delete the remote:
    influx remote delete \
      --org-id <OSS org ID> \
      --token <OSS token> \
      --id 0ooxX0xxXo0x
    

Was this page helpful?

Thank you for your feedback!


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: