Skip to content
Development documentation
This describes Keydra as it is being built and is not a released version. What it documents can change before a release.

Importing and exporting keys

Export selected keys or everything matching a pattern, and restore them — through the server's own DUMP and RESTORE, so a value survives exactly.

Moving keys in and out of a file#

Export writes the keys, their values and their expiries in the same shape the import reads. It uses the server’s own DUMP and RESTORE, so a value survives the round trip exactly — including types Keydra has no editor for.

It is not an RDB file. A snapshot is the server writing its own memory to its own disk, inside its own container, and Keydra has no filesystem there. What it can export is what it can read.

The same format is what a backup destination receives, so a file exported by hand and one written by a nightly job are the same thing.

Exporting and importing keys#

Prerequisites
  • transfer:export to export, transfer:import to import.

Procedure

To export:

  1. Open the target’s Keys page.

  2. Either select rows and use Export {count} keys, or use Export everything matching to export what the current glob matches.

  3. The file downloads.

To import:

  1. On the Keys page, open Import and export and choose the import action.

  2. Choose the file.

  3. Decide what happens to a key that already exists: replace it, or leave it alone.

  4. Confirm.

Verification

The key list updates as keys arrive — the change goes out over the notification hub, so the count moves without a rescan.

Edit this page