Dumping Stored Data
The dump
subcommand writes the contents of all stored data to the file
system. This is primarily intended for debugging but can be used to get access
to the view of the RPKI data that Routinator currently sees. This subcommand has
only one option, --output
, which specifies the directory where the
output should be written.
Three directories will be created in the output directory:
- rrdp
This directory contains all the files collected via RRDP from the various repositories. Each repository is stored in its own directory. The mapping between
rpkiNotify
URI and path is provided in therepositories.json
file. For each repository, the files are stored in a directory structure based on the components of the file as rsync URI.- rsync
This directory contains all the files collected via rsync. The files are stored in a directory structure based on the components of the file’s rsync URI.
- store
This directory contains all the files used for validation. Files collected via RRDP or rsync are copied to the store if they are correctly referenced by a valid manifest. This part contains one directory for each RRDP repository similarly structured to the
rrdp
directory and one additional directoryrsync
that contains files collected via rsync.- ta
This directory contains the trust anchor certificates. Files are stored in a directory structure two levels deep. The first level is the schema portion of the certificate’s URI, i.e.,
https
orrsync
, and the second level is the authority portion of the URI, e.g.,tal.apnic.net
. Within this second level, the certificate is stored in a file that has the hexadecimal encoding of the SHA-256 hash of the certificate’s URI as the file name with the extension.cer
appended.
New in version 0.9.0.
Changed in version 0.11.1: Stored trust anchor certificates are dumped into the ta
directory.