Merge pull request #287818 from dominicbetts/release-aio-m2-fix-links

AIO: Fix sample links for M2 release

Author: PMEds28

.openpublishing.publish.config.json

@@ -236,12 +236,6 @@
             "branch": "main",
             "branch_mapping": {}
         },
-        {
-            "path_to_root": "azure-iot-operations-samples-m2",
-            "url": "https://github.com/Azure-Samples/explore-iot-operations",
-            "branch": "release-m2",
-            "branch_mapping": {}
-        },
         {
             "path_to_root": "azure-iot-sdk-node",
             "url": "https://github.com/Azure/azure-iot-sdk-node",

articles/iot-operations/get-started-end-to-end-sample/quickstart-add-assets.md

@@ -42,12 +42,12 @@ This quickstart uses the OPC PLC simulator to generate sample data. To deploy th
 <!-- TODO: Change branch to main before merging the release branch -->
 
 ```console
-kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/release-m2/samples/quickstarts/opc-plc-deployment.yaml
+kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/quickstarts/opc-plc-deployment.yaml
 ```
 
 The following snippet shows the YAML file that you applied:
 
-:::code language="yaml" source="~/azure-iot-operations-samples-m2/samples/quickstarts/opc-plc-deployment.yaml":::
+:::code language="yaml" source="~/azure-iot-operations-samples/samples/quickstarts/opc-plc-deployment.yaml":::
 
 > [!CAUTION]
 > This configuration isn't secure. Don't use this configuration in a production environment.

articles/iot-operations/get-started-end-to-end-sample/quickstart-upload-telemetry-to-cloud.md

@@ -115,7 +115,7 @@ To create and configure a dataflow in your cluster, run the following commands i
 # [Bash](#tab/bash)
 
 ```bash
-wget https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/release-m2/samples/quickstarts/dataflow.yaml
+wget https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/quickstarts/dataflow.yaml
 sed -i 's/<NAMESPACE>/'"${CLUSTER_NAME:0:24}"'/' dataflow.yaml
 
 kubectl apply -f dataflow.yaml
@@ -124,7 +124,7 @@ kubectl apply -f dataflow.yaml
 # [PowerShell](#tab/powershell)
 
 ```powershell
-Invoke-WebRequest -Uri https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/release-m2/samples/quickstarts/dataflow.yaml -OutFile dataflow.yaml
+Invoke-WebRequest -Uri https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/quickstarts/dataflow.yaml -OutFile dataflow.yaml
 
 (Get-Content dataflow.yaml) | ForEach-Object { $_ -replace '<NAMESPACE>', $CLUSTER_NAME.Substring(0, [MATH]::Min($CLUSTER_NAME.Length, 24)) } | Set-Content dataflow.yaml
 

articles/iot-operations/includes/deploy-mqttui.md

@@ -14,12 +14,12 @@ Verify data is flowing to the MQTT broker by using the **mosquitto_sub** tool. I
     <!-- TODO: Change branch to main before merging the release branch -->
 
     ```console
-    kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/release-m2/samples/quickstarts/mqtt-client.yaml
+    kubectl apply -f https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/main/samples/quickstarts/mqtt-client.yaml
     ```
 
     The following snippet shows the YAML file that you applied:
 
-    :::code language="yaml" source="~/azure-iot-operations-samples-m2/samples/quickstarts/mqtt-client.yaml":::
+    :::code language="yaml" source="~/azure-iot-operations-samples/samples/quickstarts/mqtt-client.yaml":::
 
     > [!CAUTION]
     > This configuration isn't secure. Don't use this configuration in a production environment.