Adding adequate CLI examples for creating triggers

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/distinct_cache.md

@@ -1,4 +1,3 @@
-
 The `influxdb3 create distinct_cache` command creates a new distinct value cache.
 
 ## Usage
@@ -52,4 +51,79 @@ 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, you must:
+
+1. Create a [database](/influxdb3/version/reference/cli/influxdb3/create/database/).
+
+2. Create a [table](/influxdb3/version/reference/cli/influxdb3/create/table/) with the columns you want to cache.
+
+3. Have a valid authentication token.
+
+## Examples
+
+{{% code-placeholders "(DATABASE|TABLE|COLUMN|CACHE)_NAME" %}}
+
+### Generix syntax
+
+Use this as a template to adapt the command to your environment. 
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create distinct_cache \
+  --database DATABASE_NAME \
+  --table TABLE_NAME \
+  --column COLUMN_NAME \
+  CACHE_NAME
+```
+
+In the example above, replace the following:
+
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
+  Database name
+- {{% code-placeholder-key %}}`TABLE_NAME`{{% /code-placeholder-key %}}: 
+  Table name
+- {{% code-placeholder-key %}}`CACHE_NAME`{{% /code-placeholder-key %}}: 
+  Name of the distinct value cache to create
+- {{% code-placeholder-key %}}`COLUMN_NAME`{{% /code-placeholder-key %}}: Column to cache distinct values from
+
+### Create a distinct value cache for one column
+
+Use this simple setup to test the cache functionality for a single tag column. It’s helpful when validating basic behavior or building up incrementally.
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create distinct_cache \
+  --database my_test_db \
+  --table my_sensor_table \
+  --columns room \
+  my_room_cache
+```
+
+### Create a hierarchical cache with constraints
+
+Use this pattern when you need more control over cache structure and retention. It creates a multilevel cache with resource limits.
+
+<!--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 pitfals
+
+- `--column` is not valid—must 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

@@ -6,7 +6,10 @@ The `influxdb3 create last_cache` command creates a new last value cache.
 <!--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> \
+  [CACHE_NAME]
 ```
 
 ## Arguments
@@ -40,4 +43,79 @@ 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 last value cache, you must:
+
+Before creating a distinct value cache, you must:
+
+1. Create a [database](/influxdb3/version/reference/cli/influxdb3/create/database/).
+
+2. Create a [table](/influxdb3/version/reference/cli/influxdb3/create/table/) with the columns you want to cache.
+
+3. Have a valid authentication token.
+
+## Examples
+
+### Generic syntax
+
+{{% code-placeholders "(DATABASE|TABLE|CACHE)_NAME (TAG_COLUMN|FIELD_COLUMN)" %}}
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create last_cache \
+  --database DATABASE_NAME \
+  --table TABLE_NAME \
+  --key-columns TAG_COLUMN \
+  --value-columns FIELD_COLUMN \
+  CACHE_NAME
+```
+
+In the example above, replace the following:
+
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: Database name
+- {{% code-placeholder-key %}}`TABLE_NAME`{{% /code-placeholder-key %}}: Table name
+- {{% code-placeholder-key %}}`TAG_COLUMN`{{% /code-placeholder-key %}}: Column to use as the key in the cache
+- {{% code-placeholder-key %}}`FIELD_COLUMN`{{% /code-placeholder-key %}}: Column to store as the value in the cache
+- {{% code-placeholder-key %}}`CACHE_NAME`{{% /code-placeholder-key %}}: Optional name for the last value cache
+
+## Create a basic last value cache for one column
+
+Use this example to create a simple cache for a single key and value column:
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create last_cache \
+  --database DATABASE_NAME \
+  --table my_sensor_table \
+  --key-columns room \
+  --value-columns temp \
+  my_temp_cache
+```
+
+## Create a last value cache with multiple keys and values
+
+This example shows how to configure a more complex cache:
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create last_cache \
+  --database DATABASE_NAME \
+  --table my_sensor_table \
+  --key-columns room,sensor_id \
+  --value-columns temp,hum \
+  --count 10 \
+  --ttl 1h \
+  my_sensor_cache
+```
+
+{{% /code-placeholders %}}
+
+## Common pitfalls
+
+- All specified key and value columns must exist in the table schema.
+- Tokens must be passed with `--token` unless set via environment variable.
+- If not specified, default values are used for `--count` and `--ttl`.

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

@@ -86,4 +86,44 @@ influxdb3 create table \
   TABLE_NAME
 ```
 
+### Verification
+
+Use the following command to confirm that your table was created:
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 query \
+  --database DATABASE_NAME \
+  --token AUTH_TOKEN \
+  "SHOW TABLES"
+```
+
+If successful, you’ll see a list of tables in the specified database, including the new one. The expected output should look similar to:
+
+<!--pytest.mark.skip-->
+
+```bash
++---------------+--------------------+----------------------------+------------+
+| table_catalog | table_schema       | table_name                 | table_type |
++---------------+--------------------+----------------------------+------------+
+| public        | iox                | my_sensor_table            | BASE TABLE |
+| public        | system             | distinct_caches            | BASE TABLE |
+| public        | system             | last_caches                | BASE TABLE |
+| public        | system             | parquet_files              | BASE TABLE |
+| public        | system             | processing_engine_logs     | BASE TABLE |
+| public        | system             | processing_engine_triggers | BASE TABLE |
+| public        | system             | queries                    | BASE TABLE |
+| public        | information_schema | tables                     | VIEW       |
+| public        | information_schema | views                      | VIEW       |
+| public        | information_schema | columns                    | VIEW       |
+| public        | information_schema | df_settings                | VIEW       |
+| public        | information_schema | schemata                   | VIEW       |
++---------------+--------------------+----------------------------+------------+
+```
+
+>[!Note]
+> The `SHOW TABLES SQL` query must be run using the influxdb3 query CLI.
+> HTTP requests to /api/v3/query are not supported in local or OSS builds of {{< product-name >}}.
+
 {{% /code-placeholders %}}

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

@@ -1,12 +1,11 @@
-
 The `influxdb3 create token` command creates a new authentication token.
 
 ## Usage
 
 <!--pytest.mark.skip-->
 
 ```bash
-influxdb3 create token <COMMAND> [OPTIONS]
+influxdb3 create token <SUBCOMMAND>
 ```
 
 ## Commands
@@ -18,15 +17,36 @@ influxdb3 create token <COMMAND> [OPTIONS]
 
 ## Options
 
-| Option |              | Description                     |
-| :----- | :----------- | :------------------------------ |
-| `-h`   | `--help`     | Print help information          |
-|        | `--help-all` | Print detailed help information |
+| Option |          | Description            |
+| :----- | :------- | :--------------------- |
+|        |`--admin`| Create an admin token  |
+| `-h`   | `--help` | Print help information |
+
 
 ## Examples
 
 ### Create an admin token
 
+<!--pytest.mark.skip-->
+
 ```bash
 influxdb3 create token --admin
-```
+```
+
+This returns a token string. You can use it to authenticate future requests by setting it with `--token` or the `INFLUXDB3_AUTH_TOKEN` environment variable.
+
+### Use the token to create a database
+
+<!--pytest.mark.skip-->
+
+```bash
+influxdb3 create database \
+  --token YOUR_ADMIN_TOKEN \
+  my_new_database
+```
+
+> [!Tip] 
+> Set the token as an environment variable to simplify repeated commands:
+> ```bash 
+> export INFLUXDB3_AUTH_TOKEN=YOUR_ADMIN_TOKEN
+> ```