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
Working sets: Config command + self-describing images fully work in the gateway (#219)
* Add config set and get for working sets.
* Support config and secrets for images with working sets.
* Fix tests after changes.
Simplify tests.
* Lint fixes.
* Add config deletion.
* Comment update.
* Update docs.
* feat: Add workingsets to client output
Show which workingsets a client is connected to as part of it's JSON
output.
* review: one working set
Update the logic to only support one working set per client.
* fix: lint
---------
Co-authored-by: Bobby House <[email protected]>
-`--set`: Format is `<server-name>.<config-key>=<value>` (can be specified multiple times)
168
+
-`--get`: Format is `<server-name>.<config-key>` (can be specified multiple times)
169
+
-`--del`: Format is `<server-name>.<config-key>` (can be specified multiple times)
170
+
-`--get-all`: Retrieves all configuration values from all servers in the working set
171
+
-`--format`: Output format - `human` (default), `json`, or `yaml`
172
+
173
+
**Important notes:**
174
+
- The server name must match the name from the server's snapshot (not the image or source URL)
175
+
- Use `docker mcp workingset show <working-set-id> --format yaml` to see available server names
176
+
- Configuration changes are persisted immediately to the working set
177
+
- You cannot both `--set` and `--del` the same key in a single command
178
+
-**Note**: Config is for non-sensitive settings. Use secrets management for API keys, tokens, and passwords.
179
+
180
+
### Managing Secrets for Working Set Servers
181
+
182
+
Secrets provide secure storage for sensitive values like API keys, tokens, and passwords. Unlike configuration values, secrets are stored securely and never displayed in plain text.
183
+
184
+
```bash
185
+
# Set a secret for a server in a working set
186
+
docker mcp secret set github.pat=ghp_xxxxx
187
+
```
188
+
189
+
**Secret format:**
190
+
- Format is `<server-name>.<secret-key>=<value>`
191
+
- The server name must match the name from the server's snapshot
192
+
- Secrets are stored in Docker Desktop's secure secret store
193
+
194
+
**Current Limitation**: Secrets are scoped across all servers rather than for each working set. We plan to address this.
195
+
126
196
### Exporting Working Sets
127
197
128
198
Export a working set to a file for backup or sharing:
0 commit comments