influxdb3 delete trigger
The influxdb3 delete trigger command deletes a processing engine trigger.
Usage
# Syntax
influxdb3 delete trigger [OPTIONS] --database <DATABASE_NAME> <TRIGGER_NAME>Arguments
- TRIGGER_NAME: The name of the trigger to delete.
Options
| Option | Description | |
|---|---|---|
-H | --host | Host URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181) |
-d | --database | (Required) Name of the database to operate on |
--token | (Required) Authentication token | |
--force | Force delete even if the trigger is active | |
--tls-ca | Path to a custom TLS certificate authority (for self-signed or internal certificates) | |
--tls-no-verify | Disable TLS certificate verification (Not recommended in production, useful for self-signed certificates) | |
-h | --help | Print help information |
--help-all | Print detailed help information |
Option environment variables
You can use the following environment variables to set command options:
| Environment Variable | Option |
|---|---|
INFLUXDB3_HOST_URL | --host |
INFLUXDB3_DATABASE_NAME | --database |
INFLUXDB3_AUTH_TOKEN | --token |
INFLUXDB3_TLS_NO_VERIFY | --tls-no-verify |
Examples
In the examples below, replace the following:
DATABASE_NAME: Database nameAUTH_TOKEN: Authentication tokenTRIGGER_NAME: Name of the trigger to delete
Delete a trigger
influxdb3 delete trigger \
--database DATABASE_NAME \
--token AUTH_TOKEN \
TRIGGER_NAMEForce delete an active trigger
influxdb3 delete trigger \
--force \
--database DATABASE_NAME \
--token AUTH_TOKEN \
TRIGGER_NAMEWas this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB 3 Enterprise and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support. Customers using a trial license can email trial@influxdata.com for assistance.