)]}'
{
  "commit": "c33cdc3359627245f605fbc1ab0084e03f30837c",
  "tree": "80c334129d8cc9a4928833360f7e4a14867960a6",
  "parents": [
    "de94bc29b75c03e003662ab9373b913e99662edf"
  ],
  "author": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Fri Sep 20 09:10:52 2019 +0200"
  },
  "committer": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Fri Sep 20 09:14:20 2019 +0200"
  },
  "message": "validate_descriptor.py: new option for validate charms\n\nDefault behaviour is NOT to validate whether the charm is in the folder.\nThe rationale is that this tool is intended to validate only the descriptor,\nnot the package. Validating the package requires more aspects to be\ntaken into account, not only the charm\nMoreover, in a CICD for a VNF vendor, charms can be created and tested\nindependently from the descriptors and only be merged in the same folder\nin the last step.\n\nChange-Id: I33aa986493931df463fa8f9d2c6cda2e4be45cf9\nSigned-off-by: garciadeblas \u003cgerardo.garciadeblas@telefonica.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9fe751a6f79a3795a02cb513b89d604c408054e8",
      "old_mode": 33261,
      "old_path": "descriptor-packages/tools/validate_descriptor.py",
      "new_id": "3c6dd4198dac4a0fcfa384d0fd69e36e40a13945",
      "new_mode": 33261,
      "new_path": "descriptor-packages/tools/validate_descriptor.py"
    }
  ]
}
