libvirt/tests/virnetdaemondata
..
input-data-admin-server-names.json
input-data-admin.json
input-data-anon-clients.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
input-data-client-auth-pending-failure.json
input-data-client-auth-pending.json tests: validate private data / pre / post exec hooks for RPC APIs 2018-02-02 13:00:48 +00:00
input-data-client-ids.json
input-data-client-timestamp.json
input-data-initial.json remote: delete the avahi mDNS support 2019-06-21 12:59:42 +01:00
input-data-no-keepalive-required.json tests: validate private data / pre / post exec hooks for RPC APIs 2018-02-02 13:00:48 +00:00
output-data-admin-server-names.json
output-data-admin.json
output-data-anon-clients.json
output-data-client-auth-pending.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-client-ids.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-client-timestamp.json
output-data-initial.json rpc: avoid unlinking sockets passed in from systemd 2019-07-12 16:55:39 +01:00
output-data-no-keepalive-required.json
README

   virnetservertest data files
   ===========================

The various input-data-*.json files are a record of all the historical
formats that libvirt has been able to produce data for. Everytime a
new field is added to the JSON output, a *new* input data file should
be created. We must not add new fields to existing input-data files,
nor must we ever re-structure them if code changes, as we must check
new code handles the legacy formats.

The various output-data-*.json files are the record of what the *new*
JSON output should look like for the correspondingly named input-data
file. It is permissible to change the existing output-data-*.json
files if the format we save in is updated.