Reference: Export and import
Reference for the "Export and import" group of qargi commands: every verb with its arguments, options and examples, generated from the release.
Updated
qargi export #
Save a project's setup, definitions and memories to one file.
Writes one archive of the parts you select: config (project answers, instances, profiles, the skill and tool library), definitions (the cloud agents, deployments and environment as they are now, secrets removed), memories (every note of the memory and reference stores), state (session tracker, audit log) and credentials (token files; only in an encrypted archive). It asks what to include and for an optional password; with one, the whole archive is encrypted by gpg (AES-256) and the password never goes into a command line. It only reads: nothing is changed or deleted.
qargi export [OPTIONS]
| Option | Argument | What it does |
|---|---|---|
--project | NAMES | only these projects, comma separated (default: ask, or all) |
--only | PARTS | the parts: config, definitions, memories, state, credentials (default: ask) |
--out | FILE | the file to write (default: qargi-export-<time>.tar.gz[.gpg] here) |
--password-file | FILE | encrypt with the first line of this file |
--no-encrypt | write the archive without a password (for scripts) |
qargi export
qargi export --project acme --only config,memories --no-encrypt --out acme.tar.gzqargi import #
Restore from an export, choosing what and how.
Reads an archive made by qargi export (asking for the password when it is encrypted), shows what is inside, asks which parts and projects to import and, for each part, how to treat what already exists: merge (add what is missing), overwrite (also replace what differs) or replace (make it match the archive, removing the rest). It then prints the plan and writes nothing until you confirm; replaced and removed items are saved under the state directory first. The archive is treated as untrusted data: names and checksums are verified. Definitions are restored as files only (rebuild with provision). Memory notes go to the stores named in the project's answers. An archive's project answers never add or change models.extensions or models.accept_no_barrier (they take a plan token and an approval: qargi provider enable, disable, accept): the stored value stays, or the key is left out, and a note says so. It asks at a terminal; --dry-run shows the plan without one.
qargi import FILE [OPTIONS]
| Option | Argument | What it does |
|---|---|---|
--only | PARTS | the parts to import (default: ask) |
--project | NAMES | only these projects of the archive, comma separated |
--mode | MODE | merge, overwrite or replace for every part (default: ask for each) |
--password-file | FILE | the password is the first line of this file |
--dry-run | print the plan and stop; changes nothing |
qargi import acme.tar.gz.gpg
qargi import acme.tar.gz --dry-run --only memories