)]}'
{
  "commit": "2b5a566395883b7d1959344bc725186bda441d01",
  "tree": "af93ea5893d1cda6485223cad20fa7c3b7803b94",
  "parents": [
    "93212b37ea8f5918e2185f4e9ddb4f92e29bd42b"
  ],
  "author": {
    "name": "Adam Israel",
    "email": "adam.israel@canonical.com",
    "time": "Wed Jul 18 13:06:29 2018 -0400"
  },
  "committer": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Thu Aug 23 15:42:49 2018 +0100"
  },
  "message": "Extend data-type to initial-config-primitive\n\nThe config-primitive defines a data-type, which is an enumerator of\nSTRING, INTEGER, and BOOLEAN, that informs consumers of the VNFD of what\ntype to treat the value as.\n\nYang itself is loosely typed, treating everything as a string, but\nspecifying the data-type is required when integrating with\nstrongly-typed languages. We\u0027ve experienced this issue, documented in\nbug #502, where the service primitives defined via the VCA are\nstrongly-typed and will fail if used with a primitive expecting a\nnon-STRING value.\n\nThis extends the data-type key to initial-config-primitive, allowing the\noperator to define what type of data is expected. This will then be\nconsumed by N2VC to properly convert the value appropriately.\n\nSigned-off-by: Adam Israel \u003cadam.israel@canonical.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ba917c0b5093827d242a2443ab39b3076b86c605",
      "old_mode": 33188,
      "old_path": "models/yang/mano-types.yang",
      "new_id": "9fb3713659824677f6935b44429cc8e827d5470c",
      "new_mode": 33188,
      "new_path": "models/yang/mano-types.yang"
    }
  ]
}