)]}'
{
  "commit": "66d2361a174d7892c9ba049e78a1c30a6bdf8ad4",
  "tree": "f1af2468afac895db15aa3fd93904de8d1b40d0c",
  "parents": [
    "f315815e29aaa025ade0500a1943803b1659376f"
  ],
  "author": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Wed Jan 12 09:58:50 2022 +0100"
  },
  "committer": {
    "name": "beierlm",
    "email": "mark.beierl@canonical.com",
    "time": "Tue Feb 15 21:10:11 2022 +0100"
  },
  "message": "Silent output when deleting ns osm in k8s cluster\n\nThe installation of the local k8s cluster with install_kubeadm_cluster.sh\nraised an error message when deleting the namespace \"osm\". That NS is\ndeleted as a previous step to the deployment of OSM pods, just to make sure\nthat we start from a clean NS.\n\nIn principle, the error from kubectl should appear always in clean\ninstallations. For that reason, the output of the command is redirected\nto /dev/null to avoid confusion for the end user.\n\nChange-Id: I4e38cb2c727683215d8b331a4780feeec98fbe5d\nSigned-off-by: garciadeblas \u003cgerardo.garciadeblas@telefonica.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f31889cb9531b9e2fe6a330f0a8e52d0bdc3631e",
      "old_mode": 33261,
      "old_path": "installers/install_kubeadm_cluster.sh",
      "new_id": "d610bb68e0e67b42b3df92e1083579f4d46d4bf1",
      "new_mode": 33261,
      "new_path": "installers/install_kubeadm_cluster.sh"
    }
  ]
}