File Support

Should the checksums just be fields on the serializer or should I do something like a checksum dictionary mapping checksum type to its value:

"checksums":  {
   "sha256": "abcdef..."
    ...
}

+1 to the "checksum" key which contains keys of the algorithm name (as you gave an example of)

After talking it over on IRC, we decided to just include the checksum fields on the file. For example:

        {
            "_artifact": "/pulp/api/v3/artifacts/f523664e-d291-427b-b260-198598c42ae0/",
            "_created": "2019-05-22T21:09:31.343339Z",
            "_href": "/pulp/api/v3/content/file/files/2b347487-c5f9-48bd-9a15-aaa79fae851a/",
            "_type": "file.file",
            "md5": "f4e4ee897387d9061e5d6a17d3991ff3",
            "relative_path": "test.iso",
            "sha1": "08e282883a0f20b24414e9e5e1f21aedba008ff2",
            "sha224": "f80f493561e579352ce24beeb9a2c71d1f1a8f7525782c9ba8e1f244",
            "sha256": "582f1729b0c15eacbb7d02a553c0a96a39f817135c15ac4190aef96e45c4b65d",
            "sha384": "ad3e4cb414ee360477c54d0db3369497fb2b8858f6328c792112f54327b394716c2e5a86caa3989960e4f27ec274a49f",
            "sha512": "4f3ca80d512fa86af762a1883a31b6a47da825368a42bfcadeb824e849f76202ebe9529e5be1a911ec4a92b5da3f4eecce95cd6a5d2b5cda3b5dd
ccf5aadf5c4"
        }