Skip to content

Commit 6ef44d6

Browse files
KorayErkanKorayErkan
authored
Merge pull request #387 from VirtualMetric:consolidate-local-includes
Consolidate local reusable MDX content into src/includes
2 parents ebac33b + ae9aeae commit 6ef44d6

28 files changed

+39
-90
lines changed

‎docs/configuration/devices/ipfix.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import AppProtocols from "./_app-protocols.mdx";
2-
31
# IPFix
42

53
<span className="theme-doc-version-badge badge badge--secondary">Push</span>
@@ -147,7 +145,7 @@ Multiple flow types can be collected through a single device:
147145
Each flow type requires its own port. Ensure no port conflicts exist between different collectors.
148146
:::
149147

150-
<AppProtocols />
148+
<Include id="devices-app-protocols" />
151149

152150
<ExampleGrid>
153151
<CommentCol>

‎docs/configuration/devices/netflow.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import AppProtocols from "./_app-protocols.mdx"
2-
31
# NetFlow
42

53
<span className="theme-doc-version-badge badge badge--secondary">Push</span>
@@ -147,7 +145,7 @@ Collecting flows from older network devices is possible:
147145
</CodeCol>
148146
</ExampleGrid>
149147

150-
<AppProtocols />
148+
<Include id="devices-app-protocols" />
151149

152150
<ExampleGrid>
153151
<CommentCol>

‎docs/configuration/devices/sflow.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import AppProtocols from "./_app-protocols.mdx"
2-
31
# sFlow
42

53
<span className="theme-doc-version-badge badge badge--secondary">Push</span>
@@ -147,7 +145,7 @@ Multiple sFlow agents can be used for collection:
147145
All sFlow agents must be configured to send to the same collector port.
148146
:::
149147

150-
<AppProtocols />
148+
<Include id="devices-app-protocols" />
151149

152150
<ExampleGrid>
153151
<CommentCol>

‎docs/configuration/targets/aws/amazon-redshift.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import S3MultipartIamNote from '../_s3-multipart-iam-note.mdx';
2-
31
# Amazon Redshift
42

53
<span className="theme-doc-version-badge badge badge--secondary">Amazon AWS</span><span className="theme-doc-version-badge badge badge--secondary">Data Warehouse</span>
@@ -200,7 +198,7 @@ The Redshift target requires two sets of permissions: one for S3 staging operati
200198
|`s3:DeleteObject`|Clean up staged files after COPY|
201199
|`s3:AbortMultipartUpload`|Abort failed multipart uploads|
202200

203-
<S3MultipartIamNote />
201+
<Include id="targets-s3-multipart-iam-note" />
204202

205203
Minimum IAM policy for DataStream:
206204

‎docs/configuration/targets/aws/amazon-s3.mdx‎

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
import BucketRouting from '../_bucket-routing.mdx';
2-
import FileFormats from '../_file-formats.mdx';
3-
import S3MultipartIamNote from '../_s3-multipart-iam-note.mdx';
4-
51
# Amazon S3
62

73
<span className="theme-doc-version-badge badge badge--secondary">Amazon AWS</span><span className="theme-doc-version-badge badge badge--secondary">Long Term Storage</span>
@@ -140,7 +136,7 @@ When using IAM role-based authentication, the following permissions are required
140136
|`s3:PutObject`|Upload log files to bucket (also covers multipart upload lifecycle)|
141137
|`s3:AbortMultipartUpload`|Abort failed multipart uploads|
142138

143-
<S3MultipartIamNote />
139+
<Include id="targets-s3-multipart-iam-note" />
144140

145141
Minimum IAM policy:
146142

@@ -171,9 +167,9 @@ Minimum IAM policy:
171167
The S3 upload manager automatically switches between single-part `PutObject` and multipart upload based on the `part_size` configuration.
172168
:::
173169

174-
<FileFormats />
170+
<Include id="targets-file-formats" />
175171

176-
<BucketRouting />
172+
<Include id="targets-bucket-routing" />
177173

178174
### Templates
179175

‎docs/configuration/targets/azure/azure-blob-storage.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import ManagedIdentity from '../_managed-identity.mdx';
2-
31
# Azure Blob Storage
42

53
<span className="theme-doc-version-badge badge badge--secondary">Microsoft Azure</span><span className="theme-doc-version-badge badge badge--secondary">Long Term Storage</span>
@@ -146,7 +144,7 @@ The target supports multiple authentication methods:
146144

147145
**Function App Authentication**: When `function_app` is specified, authentication is handled through the Function App token, and direct storage credentials are not required.
148146

149-
<ManagedIdentity />
147+
<Include id="targets-managed-identity" />
150148

151149
### IAM Permissions
152150

‎docs/configuration/targets/azure/azure-data-explorer.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import ManagedIdentity from '../_managed-identity.mdx';
2-
31
# Azure Data Explorer
42

53
<span className="theme-doc-version-badge badge badge--secondary">Microsoft Azure</span><span className="theme-doc-version-badge badge badge--secondary">Observability</span>
@@ -73,7 +71,7 @@ The following fields are used to define the target:
7371

7472
(2) = Required if you want a catch-all table for unmatched events, or if not using the tables array
7573

76-
<ManagedIdentity />
74+
<Include id="targets-managed-identity" />
7775

7876
### Ingestion Options
7977

‎docs/configuration/targets/azure/azure-event-hubs.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import ManagedIdentity from '../_managed-identity.mdx';
2-
31
# Azure Event Hubs
42

53
<span className="theme-doc-version-badge badge badge--secondary">Microsoft Azure</span><span className="theme-doc-version-badge badge badge--secondary">Real-time Messaging</span>
@@ -78,7 +76,7 @@ EventHubs target supports two authentication methods:
7876

7977
**Method 3: Managed Identity**
8078

81-
<ManagedIdentity />
79+
<Include id="targets-managed-identity" />
8280

8381
### Partition Configuration
8482

‎docs/configuration/targets/azure/azure-monitor.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import ManagedIdentity from '../_managed-identity.mdx';
2-
31
# Azure Monitor Logs
42

53
<span className="theme-doc-version-badge badge badge--secondary">Microsoft Azure</span><span className="theme-doc-version-badge badge badge--secondary">Logging & Monitoring</span>
@@ -72,7 +70,7 @@ The following fields are used to define the target:
7270

7371
\* = Conditionally required. Use either direct authentication (`tenant_id`, `client_id`, `client_secret`) OR Director Proxy forwarding (`function_app`, `function_token`), OR omit all credentials to use Managed Identity.
7472

75-
<ManagedIdentity />
73+
<Include id="targets-managed-identity" />
7674

7775
### Table Configuration
7876

‎docs/configuration/targets/azure/azure-service-bus.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
import ManagedIdentity from '../_managed-identity.mdx';
2-
31
# Azure Service Bus
42

53
<span className="theme-doc-version-badge badge badge--secondary">Microsoft Azure</span><span className="theme-doc-version-badge badge badge--secondary">Message Queue</span>
@@ -83,7 +81,7 @@ Azure Service Bus target supports two authentication methods:
8381

8482
**Method 3: Managed Identity**
8583

86-
<ManagedIdentity />
84+
<Include id="targets-managed-identity" />
8785

8886
### Message Properties
8987

0 commit comments

Comments
 (0)