Skip to content

Commit c99a445

Browse files
committed
Fix file name
1 parent 9a3f3ca commit c99a445

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/iot-operations/connect-to-cloud/tutorial-mqtt-bridge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -520,7 +520,7 @@ Currently, Bicep doesn't apply to deploy MQTT client.
520520

521521
# [Kubernetes (preview)](#tab/kubernetes)
522522

523-
Download `client.yaml` deployment from the GitHub sample repository.
523+
Download `mqtt-client.yaml` deployment from the GitHub sample repository.
524524

525525
> [!IMPORTANT]
526526
> Don't use the MQTT client in production. The client is for testing purposes only.

articles/iot-operations/manage-mqtt-broker/howto-test-connection.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Before you begin, [install or configure IoT Operations](../get-started-end-to-en
3737

3838
The first option is to connect from within the cluster. This option uses the default configuration and requires no extra updates. The following examples show how to connect from within the cluster using plain Alpine Linux and a commonly used MQTT client, using the service account and default root CA certificate.
3939

40-
Download `client.yaml` deployment from the GitHub sample repository.
40+
Download `mqtt-client.yaml` deployment from the GitHub sample repository.
4141

4242
> [!IMPORTANT]
4343
> Don't use the MQTT client in production. The client is for testing purposes only.

0 commit comments

Comments
 (0)