)]}'
{
  "commit": "eef6ef54490c2fe997b872d3324bfb03f23e178a",
  "tree": "7dc13e7306b2aa67a9d763e0b51fc97f31a2609c",
  "parents": [
    "f6fbe42594c64f6cacfaf1798568e3ff40712240"
  ],
  "author": {
    "name": "aguilard",
    "email": "e.dah.tid@telefonica.com",
    "time": "Thu Nov 02 16:52:56 2023 +0000"
  },
  "committer": {
    "name": "aguilard",
    "email": "e.dah.tid@telefonica.com",
    "time": "Mon Nov 13 12:19:32 2023 +0200"
  },
  "message": "Fix bug 2302: IP ranges management in Azure not working properly\n\nOSM uses a specific vnet to create NS or VNF subnets when instantiating on\nAzure. The vnets allow more than one address prefix, but RO only try to\nallocate new subnets in the range defined in first place, ignoring the rest.\n\nChange-Id: I9792caf2a468e60b6762567a9b4a90d0f1646b39\nSigned-off-by: aguilard \u003ce.dah.tid@telefonica.com\u003e\n(cherry picked from commit 5d27a33f4c8f6a9bc5f6ca20f844a124a5d8b223)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "15c3cadc349687c159f6f3668486478a89c162ff",
      "old_mode": 33261,
      "old_path": "RO-VIM-azure/osm_rovim_azure/vimconn_azure.py",
      "new_id": "06bc97031666e1a9c9a80c6cfb91032dacecc942",
      "new_mode": 33261,
      "new_path": "RO-VIM-azure/osm_rovim_azure/vimconn_azure.py"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "0181013cfb90fea4cd59c2efdb972c02fb2d543b",
      "new_mode": 33188,
      "new_path": "releasenotes/notes/fix_bug_2302-3432828f06200186.yaml"
    }
  ]
}