)]}'
{
  "commit": "5c9affdd9a2baff2166146f4743fe75009b32eab",
  "tree": "eae6e05d4af6e0395f4f0e1fbe62145a0b6f6684",
  "parents": [
    "7befae663c6aa99343cb2c90e74ee2e3bc676559"
  ],
  "author": {
    "name": "Julia Kreger",
    "email": "juliaashleykreger@gmail.com",
    "time": "Fri Mar 12 11:19:52 2021 -0800"
  },
  "committer": {
    "name": "Julia Kreger",
    "email": "juliaashleykreger@gmail.com",
    "time": "Tue Jun 22 14:49:12 2021 +0000"
  },
  "message": "Use specific credentials for tempest plugin setup\n\nThe tempest plugin expects the classic environment variables\nto be present for credentials to access the cloud, but this is\nwrong in cases where we\u0027re trying to setup system\nscoped services and need to remove the environment variables\nthat was being used.\n\nInstead, change the plugin to use the os-cloud entry definitions,\nand specifically in this case devstack-admin which makes sense\nuntil we begin to start to make tempest itself scope aware.\n\nWe likely will want to change the environment variables from being\nregistered in devstack at some point and completely shift towards\npassing an-os-cloud parameter, but that is outside the scope of\nthis change as doing so will likely break all plugins.\n\nChange-Id: I8d4ec68f116eea07bc7346f939e134fa2e655eac\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d835c68d4a320c0bf8c123fbb0e3d000c4c8665d",
      "old_mode": 33188,
      "old_path": "lib/tempest",
      "new_id": "545018b4a400aa9d8f948c0ed60e6d5265fd9627",
      "new_mode": 33188,
      "new_path": "lib/tempest"
    }
  ]
}
