)]}'
{
  "log": [
    {
      "commit": "da5079e66a03bc0042119161dfa7dbc1f800d62a",
      "tree": "246eef7fcdf70676fc395ccb876af2d5a0463f00",
      "parents": [
        "fdaa25c217569f99e555c67e6315af16e32a60b7"
      ],
      "author": {
        "name": "Jan Klare",
        "email": "jan.klare@bisdn.de",
        "time": "Fri Sep 29 11:43:31 2023 +0200"
      },
      "committer": {
        "name": "Jan Klare",
        "email": "jan.klare@bisdn.de",
        "time": "Fri Sep 29 11:43:31 2023 +0200"
      },
      "message": "Pin ansible-galaxy version of lf-recommended-tools\n\n* currently building new AMI images is not possible due to a version\n  conflict between the nodejs package installed by the newest version of\n  lf-recommended-tools from the upstream nodejs debian repository and\n  the nodejs-dev version installed by the onf-playbook from the default\n  debian repositories of ubuntu 18.04\n* to solve this conflict for now, we should pull both nodejs and\n  nodejs-dev from the default debian repository for ubuntu 18.04 as done\n  before\n* to avoid installing the new nodejs repository and nodejs itself by\n  running the newer version of lf-recommended-tools from ansible-galaxy,\n  we need to generate our own requirements.yaml\n  (packer/ansible-galaxy-requirements.yaml) to pin the version of\n  lf-recommended-tools to the last commit before the installation of\n  nodejs was added\n* in addition to adding our own requirements file, we also need to\n  replace the scripted call of ansible-galaxy.sh from the upstream\n  repository with a simple `ansible-galaxy install ... -r` while handing\n  over our own ansible-galaxy-requirements.yaml as the requirements file\n  (instead of using the one from upstream)\n\nSigned-off-by: Jan Klare \u003cjan.klare@bisdn.de\u003e\nChange-Id: I2f7d07afb229a065eedafeb891ef040e6cfe4f10\n"
    }
  ]
}