state store update

Signed-off-by: Ryan Winter <[email protected]>

Author: ryanwinter

articles/iot-operations/create-edge-apps/concept-about-state-store-protocol.md

@@ -8,16 +8,17 @@ ms.topic: concept-article
 ms.date: 10/30/2024
 
 # CustomerIntent: As a developer, I want understand what the MQTT broker state store protocol is, so
-# that I can implement a client app to interact with the MQ state store.
+# that I can implement a client app to interact with the state store.
 ms.service: azure-iot-operations
 ---
 
-# MQTT broker state store protocol
+# State store protocol
 
-The MQ state store is a distributed storage system within the Azure IoT Operations cluster. The state store offers the same high availability guarantees as MQTT messages in MQTT broker. According to the MQTT5/RPC protocol guidelines, clients should use MQTT5 to interact with the MQ state store. This article provides protocol guidance for developers who need to implement their own MQTT broker state store clients. 
+The state store is a distributed storage system within the Azure IoT Operations cluster. The state store offers the same high availability guarantees as MQTT messages in MQTT broker. According to the MQTT5/RPC protocol guidelines, clients should use MQTT5 to interact with the state store. This article provides protocol guidance for developers who need to implement their own MQTT broker state store clients. 
 
-## State store protocol overview
-The MQ state store supports the following commands:
+## Overview
+
+The state store supports the following commands:
 
 - `SET` \<keyName\> \<keyValue\> \<setOptions\>
 - `GET` \<keyName\>
@@ -71,7 +72,7 @@ sequenceDiagram
 
 The commands `SET`, `GET`, and `DEL` behave as expected.
 
-The values that the `SET` command sets, and the `GET` command retrieves, are arbitrary binary data. The size of the values is only limited by the maximum MQTT payload size, and resource limitations of MQ and the client.
+The values that the `SET` command sets, and the `GET` command retrieves, are arbitrary binary data. The size of the values is only limited by the maximum MQTT payload size, and resource limitations of MQTT broker and the client.
 
 ### `SET` options
 
@@ -421,7 +422,7 @@ The topic is defined in the following example. The `clientId` is an upper-case h
 clients/statestore/v1/FA9AE35F-2F64-47CD-9BFF-08E2B32A0FE8/{clientId}/command/notify/{keyName}
 ```
 
-As an example, MQ publishes a `NOTIFY` message sent to `client-id1` with the modified key name `SOMEKEY` to the topic:
+As an example, MQTT broker publishes a `NOTIFY` message sent to `client-id1` with the modified key name `SOMEKEY` to the topic:
 
 ```console
 clients/statestore/v1/FA9AE35F-2F64-47CD-9BFF-08E2B32A0FE8/636C69656E742D696431/command/notify/534F4D454B4559`

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

@@ -31,7 +31,7 @@ To install the Dapr runtime, use the following Helm command:
 ```bash
 helm repo add dapr https://dapr.github.io/helm-charts/
 helm repo update
-helm upgrade --install dapr dapr/dapr --version=1.13 --namespace dapr-system --create-namespace --wait
+helm upgrade --install dapr dapr/dapr --version=1.14 --namespace dapr-system --create-namespace --wait
 ```
 
 ## Register MQTT broker pluggable components
@@ -112,7 +112,7 @@ To create the yaml file, use the following component definitions:
         value: /var/run/secrets/tokens/mqtt-client-token    
     ```
 
-1. Apply the component yaml to your cluster by running the following command:
+1. Apply the Component to your cluster by running the following command:
 
     ```bash
     kubectl apply -f components.yaml

articles/iot-operations/create-edge-apps/overview-state-store.md

@@ -0,0 +1,15 @@
+# What is the state store
+
+The state store is a distributed storage system within the Azure IoT Operations cluster. Using the State Store, applications can get/set/delete key/value pairs without needing to install additional services such as Redis. The State Store also provides versioning of the data as well as providing the primitives for building distributed locks.
+
+Like Redis, the state store uses in memory storage. Stopping the Kubernetes cluster and/or uninstalling MQ will state store data to be lost.
+
+The state store is implemented via MQTTv5. Its service is integrated directly into MQ and is automatically started when MQ starts. The state store provides the same high available as the MQ MQTT broker.
+
+The state store extends MQTT broker's authorization mechanism, allowing individual clients to have optional read and write access to specific keys. Its authentication is documented in more detail here.
+
+The state store protocol is documented in [state store protocol](concept-about-state-store-protocol.md). SDKs are available for the state store for Go, C#, and Rust. You are strongly encouraged to use an SDK if available for your language instead of implementing the protocol yourself. Additional information about the SDKs is available
+
+## CLI
+
+Ewerton tool goes here.

articles/iot-operations/toc.yml

@@ -145,6 +145,12 @@ items:
       items:
       - name: Edge apps overview
         href: create-edge-apps/edge-apps-overview.md
+      - name: State store
+        items:
+        - name: State store overview
+          href: create-edge-apps/overview-state-store.md
+        - name: About the state store protocol 
+          href: create-edge-apps/concept-about-state-store-protocol.md
       - name: Dapr apps
         items:
         - name: Deploy Dapr
@@ -153,8 +159,6 @@ items:
           href: create-edge-apps/howto-develop-dapr-apps.md
         - name: Build an event-driven app with Dapr
           href: create-edge-apps/tutorial-event-driven-with-dapr.md
-      - name: About the MQ state store protocol 
-        href: create-edge-apps/concept-about-state-store-protocol.md
       - name: Develop MQTTnet apps
         href: create-edge-apps/howto-develop-mqttnet-apps.md
     - name: Tutorials