You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Download the state store CLI from the [latest GitHub release](https://github.com/Azure-Samples/explore-iot-operations/releases?q=state-store-cli) and save it in the `state-store-cli` directory
26
+
1. Download the state store CLI from the [latest GitHub release](https://github.com/Azure-Samples/explore-iot-operations/releases?q=statestore-cli) and save it in the `statestore-cli` directory
27
27
28
28
1. **OPTIONAL**: If MQTT broker authentication is required, [install step](https://smallstep.com/docs/step-cli/installation/) to generate the required certificates
29
29
@@ -68,21 +68,21 @@ If security is a requirement, then you will need to expose the MQTT broker using
68
68
```
69
69
70
70
> [!NOTE]
71
-
> The `certs` directory will contain the following files which will be used by the state store cli tool for authenticating with the MQTT broker:
71
+
> The `certs` directory will contain the following files which will be used by the state store CLI tool for authenticating with the MQTT broker:
72
72
>
73
-
>*`broker-ca.crt`: The MQTT broker server certificate
74
-
>*`client.crt`: The device certificate for authentication with MQTT broker
75
-
>*`client.key`: The device private key for authentication with MQTT broker
73
+
>*`broker-ca.crt`: The MQTT broker server certificate
74
+
>*`client.crt`: The device certificate for authentication with MQTT broker
75
+
>*`client.key`: The device private key for authentication with MQTT broker
76
76
77
77
## Usage
78
78
79
-
For accessing help directly from the console just type`statestore --help`.
79
+
For accessing help directly from the console just type`statestore-cli --help`.
80
80
81
81
```shell
82
-
$ ./statestore --help
83
-
Allows managing key/value pairs in the MQ State Store.
82
+
$ ./statestore-cli --help
83
+
Allows managing key/value pairs in the state store.
84
84
85
-
Usage: statestore [OPTIONS] <COMMAND>
85
+
Usage: statestore-cli [OPTIONS] <COMMAND>
86
86
87
87
Commands:
88
88
get Gets the value of an existing key
@@ -92,17 +92,17 @@ Commands:
92
92
93
93
Options:
94
94
-n, --hostname <HOSTNAME>
95
-
MQ broker hostname
95
+
MQTT broker hostname
96
96
97
97
[default: localhost]
98
98
99
99
-p, --port <PORT>
100
-
MQ broker port number
100
+
MQTT broker port number
101
101
102
102
[default: 8883]
103
103
104
104
--notls
105
-
Do not use TLS for connection with MQ broker
105
+
Do not use TLS for connection with MQTT broker
106
106
107
107
-T, --cafile <CAFILE>
108
108
Trusted certificate bundle for TLS connection
@@ -122,29 +122,29 @@ Options:
122
122
-h, --help
123
123
Print help (see a summary with '-h')
124
124
125
-
-V, --version
125
+
--version
126
126
Print version
127
127
```
128
128
129
-
Help specific to each command can be printed through calling `statestore <command> --help`.
129
+
Help specific to each command can be printed through calling `statestore-cli<command> --help`.
130
130
131
131
```shell
132
-
$ ./statestore get --help
132
+
$ ./statestore-cli get --help
133
133
Gets the value of an existing key
134
134
135
-
Usage: statestore get [OPTIONS] --key <KEY>
135
+
Usage: statestore-cli get [OPTIONS] --key <KEY>
136
136
137
137
Options:
138
138
-k, --key <KEY>
139
139
Device State Store key name to retrieve
140
140
-f, --valuefile <VALUEFILE>
141
141
File where to write the key value. If not provided, the value is written to stdout
142
142
-n, --hostname <HOSTNAME>
143
-
MQ broker hostname [default: localhost]
143
+
MQTT broker hostname [default: localhost]
144
144
-p, --port <PORT>
145
-
MQ broker port number [default: 8883]
145
+
MQTT broker port number [default: 8883]
146
146
--notls
147
-
Do not use TLS for connection with MQ broker
147
+
Do not use TLS for connection with MQTT broker
148
148
-T, --cafile <CAFILE>
149
149
Trusted certificate bundle for TLS connection
150
150
-C, --certfile <CERTFILE>
@@ -164,15 +164,15 @@ Options:
164
164
For the examples below, assume:
165
165
166
166
- The MQTT broker is named `mybroker.net`, on port `8883` or `1883`
167
-
- The MQTT brokers trusted CA certificate bundle is available locally as saved locally at `./certs/broker-ca.crt`
168
-
- Client certificates are setin the AIO MQ Broker, and saved locally at `./certs/client.crt` and `./certs/client.key`.
167
+
- The MQTT broker trust bundle is available locally at `./certs/broker-ca.crt`
168
+
- Client certificates are saved locally at `./certs/client.crt` and `./certs/client.key`
0 commit comments