)]}'
{
  "commit": "91f26241c01b5862022b193741a4408f74689a9e",
  "tree": "b1c43ce90bc76e461f2b514fd07426cc5d943a9f",
  "parents": [
    "13da5b3a190d63baf7bccf035a2e7c3e543b09d5"
  ],
  "author": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Wed Jan 12 09:58:50 2022 +0100"
  },
  "committer": {
    "name": "garciadeblas",
    "email": "gerardo.garciadeblas@telefonica.com",
    "time": "Thu Jan 20 17:39:48 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: I65b90675194848f3968a9c192427224652e3087f\nSigned-off-by: garciadeblas \u003cgerardo.garciadeblas@telefonica.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "972fef16f5559c103a9eb108b52f013b025636e0",
      "old_mode": 33261,
      "old_path": "installers/install_kubeadm_cluster.sh",
      "new_id": "1672854ae84b4abb3d206071345165b5a3e3dc16",
      "new_mode": 33261,
      "new_path": "installers/install_kubeadm_cluster.sh"
    }
  ]
}