)]}'
{
  "commit": "ad13c0a8dacbf5d5d399aa2df99313bb5fb6a39b",
  "tree": "bdf0d22810528a5c2c10e2f7efcbd0f31cbdf17a",
  "parents": [
    "f6fd39f9743cf0eb3be017c907bbe5b3ba2873ee"
  ],
  "author": {
    "name": "Brant Knudson",
    "email": "bknudson@us.ibm.com",
    "time": "Sat Mar 14 12:14:31 2015 -0500"
  },
  "committer": {
    "name": "Brant Knudson",
    "email": "bknudson@us.ibm.com",
    "time": "Mon Mar 16 20:25:14 2015 +0000"
  },
  "message": "Keystone stop using config refs\n\n - Rather than using config refs, deployments should be using a tool\n   such as chef or puppet to set the options correctly.\n\n - Config refs have a bug where you can only reference an option in\n   the DEFAULT group, which limits the usefulness, and with this\n   feature it\u0027s impossible to move any config options out of the\n   DEFAULT group, luckily this has been ignored anyways since I think\n   everyone realizes how broken it is.\n\nChange-Id: I74cae09f9d75177f8efea69e7ae981ed8f14039f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0968445dc0e8ee93965a54246364bac99c602ce6",
      "old_mode": 33188,
      "old_path": "lib/keystone",
      "new_id": "45924402488fa4b70939cce5ac9170f2091cdd14",
      "new_mode": 33188,
      "new_path": "lib/keystone"
    }
  ]
}