)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"5e46458d54e02c3b6f3fe22d5c3d5dc1297ad3b4","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"114a645c_da89c1aa","updated":"2025-03-27 14:51:32.000000000","message":"As I described in the comment in https://bugs.launchpad.net/zaqar/+bug/2103994 , \"lack\" of create_at field is not an issue bit follows the current API design. We can technically add it but need to understand any actual problem caused by lack of the field.","commit_id":"e86bacfdba83950c1e74c2a86131bcca53301b5f"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"36ac543eb27ee8eae67a91536c2d81c089233dbe","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":5,"id":"4b6c0507_772176a4","updated":"2025-08-12 12:29:24.000000000","message":"We have a few other storage drivers and these should be also updated to return created_at. We should not expose difference caused by backend to users.\n\nAlso this probably worth describing in a release note.","commit_id":"e86bacfdba83950c1e74c2a86131bcca53301b5f"}]}
