chore(influxdb3): v3.2.1 fixes request trigger spec in 3Ent. Remove Core-Ent divergence notes.

Author: jstirnaman

api-docs/influxdb3/enterprise/v3/ref.yml

@@ -1239,8 +1239,7 @@ paths:
                   db: mydb
                   plugin_filename: request.py
                   trigger_name: hello_world_trigger
-                  # trigger_specification: "request:hello-world" - For 3.2.1 (issue#6171)
-                  trigger_specification: {"request_path": {"path": "hello-world"}}
+                  trigger_specification: request:hello-world
               cron_friday_afternoon:
                 summary: Cron trigger for Friday afternoons
                 description: |
@@ -1478,17 +1477,14 @@ paths:
           For example, if you define a trigger with the following:
 
           ```json
-          trigger_specification: {"request_path": {"path": "hello-world"}}
+          trigger_specification: "request:hello-world"
           ```
-          
+
           then, the HTTP API exposes the following plugin endpoint:
             
           ```
           <INFLUXDB3_HOST>/api/v3/engine/hello-world
           ```
-
-          ***Note:*** Currently, due to a bug in InfluxDB 3 Enterprise, the request trigger specification is different from Core.
-
         in: path
         required: true
         schema:
@@ -2094,25 +2090,12 @@ components:
             - `table:TABLE_NAME` - Triggers on write events to a specific table
 
             ### On-demand triggers
-            Format: `{"request_path": {"path": "REQUEST_PATH"}}`
+            Format: `request:REQUEST_PATH`
 
             Creates an HTTP endpoint `/api/v3/engine/REQUEST_PATH` for manual invocation:
-            - `{"request_path": {"path": "hello-world"}}` - Creates endpoint `/api/v3/engine/hello-world`
-            - `{"request_path": {"path": "data-export"}}` - Creates endpoint `/api/v3/engine/data-export`
-
-            ***Note:*** Currently, due to a bug in InfluxDB 3 Enterprise, the request trigger specification is different from Core. Use the JSON object format shown above.
-
-          oneOf:
-            - type: string
-              pattern: ^(cron:[0-9 *,/-]+|every:[0-9]+[smhd]|all_tables|table:[a-zA-Z_][a-zA-Z0-9_]*)$
-            - type: object
-              properties:
-                request_path:
-                  type: object
-                  properties:
-                    path:
-                      type: string
-                      pattern: ^[a-zA-Z0-9_-]+$
+            - `request:hello-world` - Creates endpoint `/api/v3/engine/hello-world`
+            - `request:data-export` - Creates endpoint `/api/v3/engine/data-export`
+          pattern: ^(cron:[0-9 *,/-]+|every:[0-9]+[smhd]|all_tables|table:[a-zA-Z_][a-zA-Z0-9_]*|request:[a-zA-Z0-9_-]+)$
           example: cron:0 0 6 * * 1-5
         trigger_arguments:
           type: object

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

@@ -113,15 +113,3 @@ influxdb3 create trigger \
 Creating a trigger in a disabled state prevents it from running immediately. You can enable it later when you're ready to activate it.
 
 {{% /code-placeholders %}}
-
-{{% show-in "enterprise" %}}
-> [!Warning]
-> #### Request trigger specification format differs between CLI and API
-> 
-> Due to a bug in InfluxDB 3 Enterprise, the request trigger specification format differs:
-> 
-> - **CLI**: `request:<REQUEST_PATH>` (same as Core CLI and API)
-> - **Enterprise API**: `{"request_path": {"path": "<REQUEST_PATH>"}}`
-> 
-> See the [API reference](/influxdb3/enterprise/api/#operation/PostConfigureProcessingEngineTrigger) for examples. Use `influxdb3 show summary` to verify the actual trigger specification.
-{{% /show-in %}}

content/shared/influxdb3-get-started/processing-engine.md

@@ -41,18 +41,6 @@ specifications:
   The plugin receives the HTTP request headers and content, and can parse,
   process, and send the data into the database or to third-party services.
 
-{{% show-in "enterprise" %}}
-> [!Warning]
-> #### Request trigger specification format differs between CLI and API
-> 
-> Due to a bug in InfluxDB 3 Enterprise, the request trigger specification format differs:
-> 
-> - **CLI**: `request:<REQUEST_PATH>` (same as Core CLI and API)
-> - **Enterprise API**: `{"request_path": {"path": "<REQUEST_PATH>"}}`
-> 
-> See the [API reference](/influxdb3/enterprise/api/#operation/PostConfigureProcessingEngineTrigger) for examples. Use `influxdb3 show summary` to verify the actual trigger specification.
-{{% /show-in %}}
-
 ## Activate the processing engine
 
 To activate the processing engine, include the `--plugin-dir <PLUGIN_DIR>` option

content/shared/v3-core-plugins/_index.md

@@ -224,7 +224,7 @@ def process_scheduled_call(influxdb3_local, call_time, args=None):
 
 #### Create an HTTP request plugin
 
-HTTP request plugins respond to API calls using [`request:`](#trigger-on-http-requests) trigger specifications{{% show-in "enterprise" %}} (CLI) or `{"request_path": {"path": "..."}}` (HTTP API){{% /show-in %}}. Use them for:
+HTTP request plugins respond to API calls using [`request:`](#trigger-on-http-requests) trigger specifications. Use them for:
 
 - Creating custom API endpoints
 - Webhooks for external integrations
@@ -263,7 +263,7 @@ After writing your plugin:
 |------------|----------------------|-----------------|
 | Data write | `table:<TABLE_NAME>` or `all_tables` | When data is written to tables |
 | Scheduled | `every:<DURATION>` or `cron:<EXPRESSION>` | At specified time intervals |
-| HTTP request | `request:<REQUEST_PATH>`{{% show-in "enterprise" %}} (CLI) or `{"request_path": {"path": "<REQUEST_PATH>"}}` (HTTP API){{% /show-in %}} | When HTTP requests are received |
+| HTTP request | `request:<REQUEST_PATH>` | When HTTP requests are received |
 
 ### Use the create trigger command
 
@@ -367,18 +367,6 @@ To view triggers associated with a database, use the `influxdb3 show summary` co
 influxdb3 show summary --database my_database --token AUTH_TOKEN
 ```
 
-{{% show-in "enterprise" %}}
-> [!Warning]
-> #### Request trigger specification format differs between CLI and API
-> 
-> Due to a bug in InfluxDB 3 Enterprise, the request trigger specification format differs:
-> 
-> - **CLI**: `request:<REQUEST_PATH>` (same as Core CLI and API)
-> - **Enterprise API**: `{"request_path": {"path": "<REQUEST_PATH>"}}`
-> 
-> See the [API reference](/influxdb3/enterprise/api/#operation/PostConfigureProcessingEngineTrigger) for examples. Use `influxdb3 show summary` to verify the actual trigger specification.
-{{% /show-in %}}
-
 ### Pass arguments to plugins
 
 Use trigger arguments to pass configuration from a trigger to the plugin it runs. You can use this for:
@@ -600,19 +588,7 @@ Each plugin must run on a node that supports its trigger type:
 |--------------------|--------------------------|-----------------------------|
 | Data write         | `table:` or `all_tables` | Ingester nodes              |
 | Scheduled          | `every:` or `cron:`      | Any node with scheduler     |
-| HTTP request       | `request:`{{% show-in "enterprise" %}} (CLI) or `{"request_path": {"path": "..."}}` (HTTP API){{% /show-in %}} | Nodes that serve API traffic|
-
-{{% show-in "enterprise" %}}
-> [!Note]
-> #### Request trigger specification format differs between CLI and API
-> 
-> Due to a bug in InfluxDB 3 Enterprise, the request trigger specification format differs:
-> 
-> - **CLI**: `request:<REQUEST_PATH>` (same as Core CLI and API)
-> - **Enterprise API**: `{"request_path": {"path": "<REQUEST_PATH>"}}`
-> 
-> See the [API reference](/influxdb3/enterprise/api/#operation/PostConfigureProcessingEngineTrigger) for examples.
-{{% /show-in %}}
+| HTTP request       | `request:`               | Nodes that serve API traffic|
 
 For example:
 - Run write-ahead log (WAL) plugins on ingester nodes.