Skip to content

Commit 7c63884

Browse files
committed
Comment out offending lines temporarily
1 parent c8217cd commit 7c63884

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

articles/iot-operations/connect-to-cloud/overview-dataflow.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,8 +78,8 @@ The local MQTT broker message queue is stored in memory by default. You can conf
7878
## Related content
7979

8080
<!-- - [Data flows vs. data flow graphs](overview-dataflow-comparison.md)
81-
- [Data flow graphs overview](concept-dataflow-graphs.md) -->
81+
- [Data flow graphs overview](concept-dataflow-graphs.md)
8282
- [Create a data flow](howto-create-dataflow.md)
83-
- [Configure a data flow source](howto-configure-dataflow-source.md)
83+
- [Configure a data flow source](howto-configure-dataflow-source.md) -->
8484
- [Create a data flow endpoint](howto-configure-dataflow-endpoint.md)
8585
- [Tutorial: Send messages from assets to the cloud using a data flow](../end-to-end-tutorials/tutorial-upload-messages-to-cloud.md)

articles/iot-operations/develop-edge-apps/howto-configure-registry-endpoint.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -445,7 +445,7 @@ spec:
445445

446446
---
447447

448-
The built-in data flow graph transforms (map, filter, branch, concat, window) use this endpoint to pull processing artifacts from MCR. When you use `registryEndpointRef: default` in a `DataflowGraph` resource, no extra registry configuration is needed. For more information about built-in transforms, see [Data flow graphs overview](../connect-to-cloud/concept-dataflow-graphs.md).
448+
<!-- The built-in data flow graph transforms (map, filter, branch, concat, window) use this endpoint to pull processing artifacts from MCR. When you use `registryEndpointRef: default` in a `DataflowGraph` resource, no extra registry configuration is needed. For more information about built-in transforms, see [Data flow graphs overview](../connect-to-cloud/concept-dataflow-graphs.md). -->
449449

450450
> [!NOTE]
451451
> For custom WASM transforms or third-party artifacts, you need to create a separate registry endpoint that points to the registry where your artifacts are stored.
@@ -456,7 +456,7 @@ Registry endpoints support any OCI-compatible container registry, including Dock
456456

457457
## Next steps
458458

459-
- [Data flow graphs overview](../connect-to-cloud/concept-dataflow-graphs.md)
459+
<!-- - [Data flow graphs overview](../connect-to-cloud/concept-dataflow-graphs.md) -->
460460
- [Use WASM transforms in data flow graphs](../connect-to-cloud/howto-dataflow-graph-wasm.md)
461461
- [Configure data flow endpoints](../connect-to-cloud/howto-configure-dataflow-endpoint.md)
462462
- [Configure data flow profiles](../connect-to-cloud/howto-configure-dataflow-profile.md)

0 commit comments

Comments
 (0)