Skip to content

Commit 55bab26

Browse files
committed
adding show-in shortcode
1 parent 8065516 commit 55bab26

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

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

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -38,23 +38,27 @@ influxdb3 serve \
3838

3939
Replace `/path/to/plugins` with the directory where you want to store your Python plugin files. All plugin files must be located in this directory or its subdirectories.
4040

41+
{{% show-in "core,enterprise" %}}
42+
4143
### Configure distributed environments
4244

4345
If you're running multiple InfluxDB instances (distributed deployment):
4446

45-
1. Decide where plugins should run:
46-
47-
- Data processing plugins, such as WAL plugins, run on ingestor nodes
48-
- HTTP-triggered plugins run on nodes handling API requests
49-
- Scheduled plugins can run on any configured node
47+
1. Decide where plugins should run
48+
- Data processing plugins, such as WAL plugins, run on ingestor nodes
49+
- HTTP-triggered plugins run on nodes handling API requests
50+
- Scheduled plugins can run on any configured node
5051
2. Enable plugins on selected instances
51-
3. Maintain identical plugin files across all instances where plugins run. Use shared storage or file synchronization tools to keep plugins consistent
52+
3. Maintain identical plugin files across all instances where plugins run
53+
- Use shared storage or file synchronization tools to keep plugins consistent
5254

5355
> [!Note]
5456
> #### Provide plugins to nodes that run them
5557
>
5658
> Configure your plugin directory on the same system as the nodes that run the triggers and plugins.
5759
60+
{{% /show-in %}}
61+
5862
## Add a Processing engine plugin
5963

6064
A plugin is a Python file that contains a specific function signature that corresponds to a trigger type.

0 commit comments

Comments
 (0)