Convert MSGPACK to YAML
Turn MSGPACK files into YAML. The same structure and key order: binary values become base64 text, timestamps become ISO 8601 text in UTC, keys that are not text become text, and several values in a row become a list.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop MSGPACK files on the dialor turn it to pick what to do
MessagePack data as readable YAML.The same structure and key order, written as a YAML file.
What you get
One YAML file with the same structure as the MessagePack file. Keys stay in the order they had in the input.
MessagePack is binary JSON, the same values as JSON in a compact byte encoding. YAML is a text format you can open and read in any editor.
What changes
Binary values become base64 text. Timestamps become ISO 8601 text in UTC.
Keys that are not text become text.
If the file holds several values in a row, they become a list in the YAML file.
When it fails
A file that cannot be parsed stops the conversion with
input_corrupted. This happens when the input is not a MessagePack file that can be read.To go the other way, use YAML to MSGPACK.
MSGPACK and YAML.What each format is.
The formats
MessagePack
Binary JSON: the same values as JSON in a compact byte encoding.
- Extensions
- .msgpack .mpk
- MIME type
- application
/msgpack - Kind
- Text and data
YAML
YAML configuration and data files.
- Extensions
- .yaml .yml
- MIME type
- application
/yaml - Kind
- Text and data
In your code.The same MSGPACK to YAML conversion through the API, for your app or your agent.
$ cv convert report.msgpack report.yaml$ cv convert report.msgpack report.yamlQuestions.What people ask about MSGPACK to YAML.
Yes. The structure and the key order stay the same as in the MessagePack file.
They become base64 text in the YAML file.
As ISO 8601 text in UTC.
The file could not be parsed, so the conversion stops and no YAML file is produced.