)]}'
{
  "commit": "e66f7d7274d8eb6f93779275e4fe5ac07cba3aad",
  "tree": "1bc6a9850c87e8998b6d438edaab9998ab70cd3a",
  "parents": [
    "05584f89eb3f974596cd628dce31f67b39752962"
  ],
  "author": {
    "name": "Oleksandr Shyshko",
    "email": "oshyshko@mirantis.com",
    "time": "Mon Jun 24 13:28:51 2019 +0300"
  },
  "committer": {
    "name": "oshyshko",
    "email": "oshyshko@mirantis.com",
    "time": "Fri Jul 05 14:21:14 2019 +0000"
  },
  "message": "`cert_client` minion `signing_policy` list for VNC CA cert is un-hardcoded\n\n  * It needed because a service engineer is able to set arbitrary hostname for control nodes.\n    It allows to set arbitrary hostname pattern where nova_novncproxy service placement.\n\nChange-Id: I0f7188de505d7d212a9ad0649771f955bec59d12\nRelated-PROD: PROD-30917\n(cherry picked from commit 888c07e08a68312727d1ca62122b6cd2ae7fcefd)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a4583ad3066a47e6fc8da4534a07e9928ecb6e2a",
      "old_mode": 33188,
      "old_path": "salt/minion/ca/qemu-vnc_ca.yml",
      "new_id": "d787fb2bda19535ac57e97c4487782fb3eb89152",
      "new_mode": 33188,
      "new_path": "salt/minion/ca/qemu-vnc_ca.yml"
    }
  ]
}