)]}'
{
  "commit": "34a103e91a0e10147fd4decc6edd859159a7f9b1",
  "tree": "b00ddb290b829e1896c0b9368fc20c5d2eaf79c9",
  "parents": [
    "e5f1b64b6d766c20f02e0ffce7d128a502673efe"
  ],
  "author": {
    "name": "Wido den Hollander",
    "email": "wido@widodh.nl",
    "time": "Sat Sep 05 19:18:48 2026 +0000"
  },
  "committer": {
    "name": "Wido den Hollander",
    "email": "wido@widodh.nl",
    "time": "Sat Sep 05 19:18:48 2026 +0000"
  },
  "message": "Direct Routed networks: let the UI pass an operator-chosen routed id\n\nCreateL3NetworkForm only supported offerings that allocate the routed id\nautomatically; an operator-chosen id (the API\u0027s vlan parameter, like a\nShared network\u0027s VLAN tag) could be given through the API alone. Add a\n\u0027Routed ID\u0027 field to the form, shown to root admins when the selected\nL3 offering carries specifyVlan - where the API requires the id - and\nhidden otherwise, since the API then rejects the parameter and\nallocates the id from the ROUTED physical network\u0027s range.\n\nThe field\u0027s description explains what the id is: a label naming the\nper-network bridge (brdr-\u003cid\u003e) on every KVM host, unique per zone,\nnothing on the wire, and useful to choose in advance so host routing\npolicy can exist before the network does.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "78cf90618d89b20ca8385a30ee6094d68b50ece7",
      "old_mode": 33188,
      "old_path": "ui/public/locales/en.json",
      "new_id": "e1715fcc7dbfa3608225716edabc92a3951e5754",
      "new_mode": 33188,
      "new_path": "ui/public/locales/en.json"
    },
    {
      "type": "modify",
      "old_id": "b6a04e8029765f799a9ca3fa348506340844115a",
      "old_mode": 33188,
      "old_path": "ui/src/views/network/CreateL3NetworkForm.vue",
      "new_id": "7e2fd2a76a9a79f8a609416d693c11bfe58678cf",
      "new_mode": 33188,
      "new_path": "ui/src/views/network/CreateL3NetworkForm.vue"
    }
  ]
}