)]}'
{
  "commit": "cb76d133adebeda011a00b73c1df161ef3d6db8c",
  "tree": "6973745f034c1059ab97bfb446a099a4781e3d96",
  "parents": [
    "48af3094153dcbef3bf03f72f9d20a3c49d50678"
  ],
  "author": {
    "name": "Benjamin Diaz",
    "email": "bdiaz@whitestack.com",
    "time": "Tue Oct 09 15:04:24 2018 -0300"
  },
  "committer": {
    "name": "Benjamin Diaz",
    "email": "bdiaz@whitestack.com",
    "time": "Tue Oct 09 17:07:09 2018 -0300"
  },
  "message": "Adds support for cooldown-time variable in scaling-policy\n\nCooldown time defines the minimum time that needs to happen between\neach scaling action. If an alarm triggers before this has happened,\nno action should be executed. When POL receives an alarm notification\nit will check that the difference between the current time and the\nlast scaling action of the alarm\u0027s scaling policy is bigger than the\ncooldown time.\nDuring configuration of the scaling groups, POL will now store the\ncooldown time of the scaling policy. Also, it adds a new last_scale\nvar to ScalingPolicy, which has as default the oldest time supported\nby Python datetime.\n\nSigned-off-by: Benjamin Diaz \u003cbdiaz@whitestack.com\u003e\nChange-Id: I6d110ccc7f89af29500c602d05054e7ba78808a0\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dfddb3ffad799d710885b2dc6af60d30cda8214b",
      "old_mode": 33188,
      "old_path": "osm_policy_module/core/agent.py",
      "new_id": "77a290f7307ae445935b97aa63d495df686aeb2a",
      "new_mode": 33188,
      "new_path": "osm_policy_module/core/agent.py"
    },
    {
      "type": "modify",
      "old_id": "212c13bb51adf02a7d264d65d1d0b50b3713eaa8",
      "old_mode": 33188,
      "old_path": "osm_policy_module/core/database.py",
      "new_id": "5d927d0d01910c162742fb87963f024886dd97c6",
      "new_mode": 33188,
      "new_path": "osm_policy_module/core/database.py"
    }
  ]
}
