)]}'
{
  "commit": "33e8ee20a4ad087f5538e813eace1ca23243e2c5",
  "tree": "a2a64e8d765c831a66a88d9671fbcb85783ab70c",
  "parents": [
    "47a81c912323adb6ef0a8254e35de311c41efe9b"
  ],
  "author": {
    "name": "Salvatore",
    "email": "salv.orlando@gmail.com",
    "time": "Sun Oct 05 01:36:34 2014 +0200"
  },
  "committer": {
    "name": "Matthew Treinish",
    "email": "mtreinish@kortar.org",
    "time": "Tue Dec 09 11:54:02 2014 -0500"
  },
  "message": "Tempest: configure exact set of extensions to test\n\nSo far devstack configures tempest either for testing all extensions\nor a specific subset. It does not allow users for specifying a set\nof extensions which should not be exercised.\n\nThis patch adds this support. To this aim, the tempest configuration\nprocess will scan API endpoints for active extensions using the\nverify_tempest_config.py tool, and then will remove those extensions\nwhich have been explicitly disabled by the user.\n\nIf an explicit subset of extensions to enable is passed to devstack,\ntempest will use this subset, rather than the list of active\nextensions.\n\nImplements blueprint branchless-tempest-extensions\n\nChange-Id: I263bcf04668953f414a4ef18cb98c1c373e142ad\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "46c9e2691614add93d1ae6c5e487f12ef9f26ed2",
      "old_mode": 33188,
      "old_path": "lib/tempest",
      "new_id": "416fae2c31ffe912cf7608b78af5492695466d26",
      "new_mode": 33188,
      "new_path": "lib/tempest"
    }
  ]
}