qbit_manage_config
Manage qbit_manage configuration files through operations that create, update, validate, backup, restore, list, and delete configs.
Instructions
qbit manage config operations on qbit_manage. Pass operation and an arguments dict matching that operation's parameters.
qbit_manage_backup_config(filename) — Create a timestamped manual backup of a config file (keeps up to 30 per config). WRITE: this modifies your qbit_manage instance.
qbit_manage_create_config(filename, body={}) — Create a new config file (body is {"data": }). Returns 409 if the file already exists. WRITE: this modifies your qbit_manage instance.
qbit_manage_delete_config(filename) — Delete a config file permanently (a backup is created before deletion). DESTRUCTIVE: this deletes data.
qbit_manage_get_config(filename) — Fetch a parsed config file. data mirrors the YAML structure; !ENV references are preserved as "!ENV ".
qbit_manage_list_config_backups(filename) — List available backups for a config file, newest first.
qbit_manage_list_configs() — List available config files in the config directory (sensitive files like qbm_settings.yml are filtered out).
qbit_manage_restore_config_from_backup(filename) — Load a backup by name (filename is the backup file name in the path, e.g. config_20260521_100000.yml) and return its data for restoring.
qbit_manage_update_config(filename, body={}) — Update an existing config file (body is {"data": }); a timestamped backup is auto-created before writing. WRITE: this modifies your qbit_manage instance.
qbit_manage_validate_config(filename, body={}) — Validate a config through the parser without executing (body is {"data": }); defaults backfilled during validation are written back to the real config.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | No | ||
| operation | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |