)]}'
{
  "commit": "2a688440132173d493dff7c7c3760681d41e11be",
  "tree": "3dc4379fe15390fc7d3b9a948eb0fe2e7188e7de",
  "parents": [
    "563c68f3cd26bb0ed440c76f4d922590e6e4e181"
  ],
  "author": {
    "name": "Steven Hardy",
    "email": "shardy@redhat.com",
    "time": "Tue Dec 08 13:26:29 2015 +0000"
  },
  "committer": {
    "name": "Steven Hardy",
    "email": "shardy@redhat.com",
    "time": "Tue Dec 08 13:34:27 2015 +0000"
  },
  "message": "Heat - revise keystone/trusts config to avoid deprecated options\n\nThere are some inter-related changes required to avoid using legacy\nfallback/deprecated paths in heat, which result in warnings in the\nlog, e.g because we fall-back to reusing keystone auth_token\nconfiguration instead of heat specific sections.\n\nTo fix this:\n- Don\u0027t explicitly set deferred_auth_method\u003dtrusts, as this is now\n  the default (since kilo)\n- Create a new \"trustee\" section containing configuration used for\n  the password auth-plugin associated with deferred authentication\n  via trusts (support for this was added during liberty to enable\n  us to stop incorrectly using the keystone auth_token config)\n- Create a \"clients_keystone\" section to avoid falling back to the\n  legacy behavior of stealing the uri from auth_token.\n\nThis also means we can remove the FIXME and auth_token auth_uri\nmentioned by jamielennox.\n\nChange-Id: Ie34332a7aec3b9b271df0759dd6ab66b45302832\nRelated-Bug: #1300246\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fdcf5bcaadcd553a854f28f54e8567db7c10ab05",
      "old_mode": 33188,
      "old_path": "lib/heat",
      "new_id": "3666776317971d8d22a6d3a94e19c9a3a8c3b103",
      "new_mode": 33188,
      "new_path": "lib/heat"
    }
  ]
}