Adding adequate CLI examples for creating triggers

content/influxdb3/clustered/admin/tokens/database/revoke 2.md

@@ -0,0 +1,56 @@
+---
+title: Revoke a database token
+description: >
+  Use the [`influxctl token revoke` command](/influxdb3/clustered/reference/cli/influxctl/token/revoke/)
+  to revoke a token from your InfluxDB cluster and disable all
+  permissions associated with the token.
+  Provide the ID of the token you want to revoke.
+menu:
+  influxdb3_clustered:
+    parent: Database tokens
+weight: 203
+list_code_example: |
+  ```sh
+  influxctl token revoke <TOKEN_ID>
+  ```
+aliases:
+  - /influxdb3/clustered/admin/tokens/delete/
+  - /influxdb3/clustered/admin/tokens/database/delete/
+---
+
+Use the [`influxctl token revoke` command](/influxdb3/clustered/reference/cli/influxctl/token/revoke/)
+to revoke a database token from your {{< product-name omit=" Clustered" >}} cluster and disable
+all permissions associated with the token.
+
+1.  If you haven't already, [download and install the `influxctl` CLI](/influxdb3/clustered/reference/cli/influxctl/#download-and-install-influxctl).
+2.  Run the [`influxctl token list` command](/influxdb3/clustered/reference/cli/influxctl/token/list)
+    to output tokens with their IDs.
+    Copy the **token ID** of the token you want to delete.
+
+    ```sh
+    influxctl token list
+    ```
+
+3.  Run the `influxctl token revoke` command and provide the following:
+
+    - Token ID to revoke
+
+4.  Confirm that you want to revoke the token.
+
+{{% code-placeholders "TOKEN_ID" %}}
+```sh
+influxctl token revoke TOKEN_ID
+```
+{{% /code-placeholders %}}
+
+> [!Warning]
+> #### Revoking a token is immediate and cannot be undone
+> 
+> Revoking a database token is a destructive action that takes place immediately
+> and cannot be undone.
+> 
+> #### Rotate revoked tokens
+> 
+> After revoking a database token, any clients using the revoked token need to
+> be updated with a new database token to continue to interact with your
+> {{% product-name omit=" Clustered" %}} cluster.

content/shared/influxdb3-cli/create/_index.md

@@ -18,7 +18,6 @@ influxdb3 create <SUBCOMMAND>
 | [file_index](/influxdb3/version/reference/cli/influxdb3/create/file_index/)         | Create a new file index for a database or table |
 | [last_cache](/influxdb3/version/reference/cli/influxdb3/create/last_cache/)         | Create a new last value cache                   |
 | [distinct_cache](/influxdb3/version/reference/cli/influxdb3/create/distinct_cache/) | Create a new distinct value cache               |
-| [plugin](/influxdb3/version/reference/cli/influxdb3/create/plugin/)                 | Create a new processing engine plugin           |
 | [table](/influxdb3/version/reference/cli/influxdb3/create/table/)                   | Create a new table in a database                |
 | [token](/influxdb3/version/reference/cli/influxdb3/create/token/)                   | Create a new authentication token               |
 | [trigger](/influxdb3/version/reference/cli/influxdb3/create/trigger/)               | Create a new trigger for the processing engine  |

content/shared/influxdb3-cli/create/database.md

@@ -1,5 +1,6 @@
+The `influxdb3 create database` command creates a new database in your {{< product-name >}} instance.
 
-The `influxdb3 create database` command creates a new database.
+Provide a database name and, optionally, specify connection settings and authentication credentials using flags or environment variables.
 
 ## Usage
 
@@ -11,11 +12,10 @@ influxdb3 create database [OPTIONS] <DATABASE_NAME>
 
 ## Arguments
 
-- **DATABASE_NAME**: The name of the database to create.
-  Valid database names are alphanumeric and start with a letter or number.
-  Dashes (`-`) and underscores (`_`) are allowed.
+
+- **`DATABASE_NAME`**: The name of the database to create. Valid database names are alphanumeric and start with a letter or number. Dashes (-) and underscores (_) are allowed.
 
-  Environment variable: `INFLUXDB3_DATABASE_NAME`
+You can also set the database name using the `INFLUXDB3_DATABASE_NAME` environment variable.
 
 ## Options
 
@@ -29,7 +29,7 @@ influxdb3 create database [OPTIONS] <DATABASE_NAME>
 
 ### Option environment variables
 
-You can use the following environment variables to set command options:
+You can use the following environment variables instead of providing CLI options directly:
 
 | Environment Variable      | Option       |
 | :------------------------ | :----------- |
@@ -38,27 +38,30 @@ You can use the following environment variables to set command options:
 
 ## Examples
 
-- [Create a new database](#create-a-new-database)
-- [Create a new database while specifying the token inline](#create-a-new-database-while-specifying-the-token-inline)
-
-In the examples below, replace the following:
+The following examples show how to create a database.
 
+In your commands replace the following:
 - {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
   Database name
 - {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}: 
   Authentication token
 
 {{% code-placeholders "DATABASE_NAME|AUTH_TOKEN" %}}
 
-### Create a new database
+### Create a database (default)
+
+Creates a database using settings from environment variables and defaults.
 
 <!--pytest.mark.skip-->
 
 ```bash
 influxdb3 create database DATABASE_NAME
 ```
 
-### Create a new database while specifying the token inline
+### Create a database with an authentication token
+
+Creates a database using the specified arguments.
+Flags override their associated environment variables.
 
 <!--pytest.mark.skip-->
 

content/shared/influxdb3-cli/create/distinct_cache.md

@@ -1,5 +1,6 @@
+The `influxdb3 create distinct_cache` command creates a new distinct value cache for a specific table and column set in your {{< product-name >}} instance.
 
-The `influxdb3 create distinct_cache` command creates a new distinct value cache.
+Use this command to configure a cache that tracks unique values in specified columns. You must provide the database, token, table, and columns. Optionally, you can specify a name for the cache.
 
 ## Usage
 
@@ -16,10 +17,9 @@ influxdb3 create distinct_cache [OPTIONS] \
 
 ## Arguments
 
-- **CACHE_NAME**: _(Optional)_ Name for the cache.
-  If not provided, the command automatically generates a name.
+- **`CACHE_NAME`**: _(Optional)_ A name to assign to the cache. If omitted, the CLI generates a name automatically.
 
-## Options
+## Options 
 
 | Option |                     | Description                                                                                                                                                             |
 | :----- | :------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -52,4 +52,69 @@ You can use the following environment variables to set command options:
 | `INFLUXDB3_DATABASE_NAME` | `--database` |
 | `INFLUXDB3_AUTH_TOKEN`    | `--token`    |
 
-<!-- TODO: GET EXAMPLES -->
+
+## Prerequisites
+
+Before creating a distinct value cache, make sure you:
+
+1. [Create a database](/influxdb3/version/reference/cli/influxdb3/create/database/)
+
+2. [Create a table](/influxdb3/version/reference/cli/influxdb3/create/table/) that includes the columns you want to cache
+
+3. Have a valid authentication token
+
+## Examples
+
+Before running the following commands, replace the placeholder values with your own:
+
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
+  The database name
+- {{% code-placeholder-key %}}`TABLE_NAME`{{% /code-placeholder-key %}}: 
+  The name of the table to cache values from
+- {{% code-placeholder-key %}}`CACHE_NAME`{{% /code-placeholder-key %}}: 
+  The name of the distinct value cache to create
+- {{% code-placeholder-key %}}`COLUMN_NAME`{{% /code-placeholder-key %}}: The column to 
+cache distinct values from
+
+You can also set environment variables (such as `INFLUXDB3_AUTH_TOKEN`) instead of passing options inline.
+
+{{% code-placeholders "(DATABASE|TABLE|COLUMN|CACHE)_NAME" %}}
+
+### Create a distinct cache for one column
+
+Track unique values from a single column. This setup is useful for testing or simple use cases.
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create distinct_cache \
+  --database DATABASE_NAME \
+  --table TABLE_NAME \
+  --column COLUMN_NAME \
+  CACHE_NAME
+```
+
+### Create a hierarchical cache with constraints
+
+Create a distinct value cache for multiple columns. The following example tracks unique combinations of `room` and `sensor_id`, and sets limits on the number of entries and their maximum age.
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create distinct_cache \
+  --database my_test_db \
+  --table my_sensor_table \
+  --columns room,sensor_id \
+  --max-cardinality 1000 \
+  --max-age 30d \
+  my_sensor_distinct_cache
+```
+
+{{% /code-placeholders %}}
+
+## Common pitfalls
+
+- `--column` is not valid. Use `--columns`.
+- Tokens must be included explicitly unless set via `INFLUXDB3_AUTH_TOKEN`
+- Table and column names must already exist or be recognized by the engine
+

content/shared/influxdb3-cli/create/last_cache.md

@@ -1,18 +1,23 @@
-
-The `influxdb3 create last_cache` command creates a new last value cache.
+The `influxdb3 create last_cache` command creates a last value cache, which stores the most recent values for specified columns in a table. Use this to efficiently retrieve the latest values based on key column combinations.
 
 ## Usage
 
+{{% code-placeholders "DATABASE_NAME|TABLE_NAME|AUTH_TOKEN|CACHE_NAME" %}}
+
 <!--pytest.mark.skip-->
 
 ```bash
-influxdb3 create last_cache [OPTIONS] --database <DATABASE_NAME> --table <TABLE> [CACHE_NAME]
+influxdb3 create last_cache [OPTIONS] \
+  --database DATABASE_NAME \
+  --table TABLE_NAME \
+  --token AUTH_TOKEN \
+  CACHE_NAME
 ```
+{{% /code-placeholders %}}
 
 ## Arguments
 
-- **CACHE_NAME**: _(Optional)_ Name for the cache.
-  If not provided, the command automatically generates a name.
+- **CACHE_NAME**: _(Optional)_ Name for the cache. If omitted, InfluxDB automatically generates one.
 
 ## Options
 
@@ -32,12 +37,67 @@ influxdb3 create last_cache [OPTIONS] --database <DATABASE_NAME> --table <TABLE>
 
 ### Option environment variables
 
-You can use the following environment variables to set command options:
+You can use the following environment variables as substitutes for CLI options:
 
 | Environment Variable      | Option       |
 | :------------------------ | :----------- |
 | `INFLUXDB3_HOST_URL`      | `--host`     |
 | `INFLUXDB3_DATABASE_NAME` | `--database` |
 | `INFLUXDB3_AUTH_TOKEN`    | `--token`    |
 
-<!-- TODO: GET EXAMPLES -->
+## Prerequisites
+
+Before creating a last value cache, ensure you’ve done the following:
+
+- Create a [database](/influxdb3/version/reference/cli/influxdb3/create/database/).
+- Create a [table](/influxdb3/version/reference/cli/influxdb3/create/table/) with the columns you want to cache.
+- Have a valid authentication token.
+
+## Examples
+
+A last value cache stores the most recent values from specified columns in a table.
+
+### Create a basic last value cache for one column
+
+The following example shows how to track the most recent value for a single key (the last temperature for each room):
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create last_cache \
+  --database DATABASE_NAME \
+  --table my_sensor_table \
+  --token AUTH_TOKEN \
+  --key-columns room \
+  --value-columns temp \
+  my_temp_cache
+```
+
+### Create a last value cache with multiple keys and values
+
+The following example shows how to:
+
+- Use multiple columns as a composite key
+- Track several values per key combination
+- Set a cache entry limit with `--count`
+- Configure automatic expiry with `--ttl`
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create last_cache \
+  --database DATABASE_NAME \
+  --table my_sensor_table \
+  --token AUTH_TOKEN \
+  --key-columns room,sensor_id \
+  --value-columns temp,hum \
+  --count 10 \
+  --ttl 1h \
+  my_sensor_cache
+```
+
+## Usage notes 
+
+- Define the table schema to include all specified key and value columns.
+- Pass tokens using `--token`, unless you've set one through an environment variable.
+- Specify `--count` and `--ttl` to override the defaults; otherwise, the system uses default values.