Change API version

Author: PatAltimore

articles/iot-operations/create-edge-apps/howto-deploy-dapr.md

@@ -131,7 +131,7 @@ To configure authorization policies to MQTT broker, first you create a [BrokerAu
 1. Save the following yaml, which contains a BrokerAuthorization definition, to a file named `aio-dapr-authz.yaml`:
 
     ```yml
-    apiVersion: mq.iotoperations.azure.com/v1beta1
+    apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
     kind: BrokerAuthorization
     metadata:
       name: my-dapr-authz-policies

articles/iot-operations/manage-mqtt-broker/howto-configure-authentication.md

@@ -29,7 +29,7 @@ kubectl get brokerauthentication authn -n azure-iot-operations -o yaml
 The output shows the default BrokerAuthentication resource, with metadata removed for brevity:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthentication
 metadata:
   name: authn
@@ -70,7 +70,7 @@ The authentication flow ends when:
 With multiple authentication methods, MQTT broker has a fallback mechanism. For example:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthentication
 metadata: 
   name: authn
@@ -152,7 +152,7 @@ BinaryData
 X509 attributes can be specified in the *BrokerAuthentication* resource. For example, every client that has a certificate issued by the root CA `CN = Contoso Root CA Cert, OU = Engineering, C = US` or an intermediate CA `CN = Contoso Intermediate CA` receives the attributes listed.
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthentication
 metadata: 
   name: authn

articles/iot-operations/manage-mqtt-broker/howto-configure-authorization.md

@@ -43,7 +43,7 @@ The specification of a *BrokerAuthorization* resource has the following fields:
 The following example shows how to create a *BrokerAuthorization* resource that defines the authorization policies for a listener named *my-listener*.
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthorization
 metadata:
   name: "my-authz-policies"
@@ -110,7 +110,7 @@ Attribute annotations must begin with `aio-mq-broker-auth/` to distinguish them
 As the application has an authorization attribute called `authz-sat`, there's no need to provide a `clientId` or `username`. The corresponding *BrokerAuthorization* resource uses this attribute as a principal, for example:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerAuthorization
 metadata:
   name: "my-authz-policies"
@@ -156,7 +156,7 @@ kubectl edit brokerauthorization my-authz-policies
 To disable authorization, set `authorizationEnabled: false` in the BrokerListener resource. When the policy is set to allow all clients, all [authenticated clients](./howto-configure-authentication.md) can access all operations.
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerListener
 metadata:
   name: "my-listener"

articles/iot-operations/manage-mqtt-broker/howto-configure-availability-scale.md

@@ -108,7 +108,7 @@ kubectl delete broker broker -n azure-iot-operations
 Then, create a YAML file with desired settings. For example, the following YAML file configures the broker with name `broker` in namespace `azure-iot-operations` with `medium` memory profile and `distributed` mode with two frontend replicas and two backend chains with two partitions and two workers each. Also, the [encryption of internal traffic option](#configure-encryption-of-internal-traffic) is disabled.
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: Broker
 metadata:
   name: broker
@@ -178,7 +178,7 @@ The following table lists the properties of the broker advanced settings that in
 Here's an example of a *Broker* with advanced settings:
 
 ```yml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: Broker
 metadata:
   name: broker
@@ -243,7 +243,7 @@ You can configure diagnostics using the *Broker* custom resource definition (CRD
 Here's an example of a *Broker* custom resource with metrics and tracing enabled and self-check disabled:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: Broker
 metadata:
   name: broker

articles/iot-operations/manage-mqtt-broker/howto-configure-brokerlistener.md

@@ -75,7 +75,7 @@ kubectl get brokerlistener listener -n azure-iot-operations -o yaml
 The output should look similar to this, with most metadata removed for brevity:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerListener
 metadata:
   name: listener
@@ -117,7 +117,7 @@ This example shows how to create a new *BrokerListener* resource for a *Broker*
 To create these *BrokerListener* resources, apply this YAML manifest to your Kubernetes cluster:
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerListener
 metadata:
   name: my-test-listener

articles/iot-operations/manage-mqtt-broker/howto-configure-tls-auto.md

@@ -175,7 +175,7 @@ For production, check cert-manager documentation to see which issuer works best
 Modify the `tls` setting in a BrokerListener resource to specify a TLS port and Issuer for the frontends. The following is an example of a BrokerListener resource that enables TLS on port 8884 with automatic certificate management.
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerListener
 metadata:
   name: my-new-tls-listener

articles/iot-operations/manage-mqtt-broker/howto-configure-tls-manual.md

@@ -78,7 +78,7 @@ Both EC and RSA keys are supported, but all certificates in the chain must use t
 Modify the `tls` setting in a BrokerListener resource to specify manual TLS configuration referencing the Kubernetes secret. Note the name of the secret used for the TLS server certificate (`server-cert-secret` in the example previously).
 
 ```yaml
-apiVersion: mq.iotoperations.azure.com/v1beta1
+apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
 kind: BrokerListener
 metadata:
   name: manual-tls-listener

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

@@ -283,7 +283,7 @@ If you understand the risks and need to use an insecure port in a well-controlle
 1. Create a new `BrokerListener` resource without TLS settings:
 
     ```yaml
-    apiVersion: mq.iotoperations.azure.com/v1beta1
+    apiVersion: mqttbroker.iotoperations.azure.com/v1beta1
     kind: BrokerListener
     metadata:
       name: non-tls-listener