)]}'
{
  "log": [
    {
      "commit": "c781473e8e3c330669e8b27f1ffb35f657b6f132",
      "tree": "86dccb55e0dc29c0db3d0a19a267b626273e8c60",
      "parents": [
        "adf04e466dfd9938091c8fa863df1911310d7d20"
      ],
      "author": {
        "name": "Dmitry Teselkin",
        "email": "dteselkin@mirantis.com",
        "time": "Thu Feb 21 16:40:23 2019 +0300"
      },
      "committer": {
        "name": "Dmitry Teselkin",
        "email": "dteselkin@mirantis.com",
        "time": "Tue Mar 26 10:26:20 2019 +0000"
      },
      "message": "Configure /etc/default/useradd through \u0027defaults\u0027\n\nAdd linux:system:defaults:user section that aims two things:\n\n* configure /etc/default/useradd file as this file contains\n  INACTIVE parameter that should be configured according to\n  CIS 5.4.1.4\n  We have to manage entire file so a template was added.\n\n* Configure three parameters that are related to user\n  account management but configured in /etc/login.defs file.\n  These are PASS_MAX_DAYS, PASS_MIN_DAYS, PASS_WARN_AGE.\n\nMore details in README.rst\n\nRelated-Prod: PROD-23600\n\nChange-Id: Idc502af3b0f31b3fe84dc9a42e3e9ec2ead7fe3c\n(cherry picked from commit 8e903564eedcacb3812de57f53c6a93575d36088)\n"
    },
    {
      "commit": "cc4d6151e0af806a9919fb1e9dbb7cf185ec2a61",
      "tree": "a6eecf154e6acc7542a6c271036011b2ddce542a",
      "parents": [
        "db768fb47c57f9fdad9b6f254716ab5fb35329ed"
      ],
      "author": {
        "name": "Tomáš Kukrál",
        "email": "tkukral@mirantis.com",
        "time": "Mon Jul 31 15:58:31 2017 +0200"
      },
      "committer": {
        "name": "Tomáš Kukrál",
        "email": "tkukral@mirantis.com",
        "time": "Mon Jul 31 15:58:31 2017 +0200"
      },
      "message": "remove .gitreview file on github\n\nChange-Id: If25a3252244c14128089e5b7997396a8869abc7e\n"
    },
    {
      "commit": "40edd5837f3ee3bd3728570e2965b1e47e3a1a24",
      "tree": "178678a3d25ad72435ce49e049608bf7e1fcaf68",
      "parents": [
        "4d290b5eec3db30330b77e1f2fd1df1c2fb8c404"
      ],
      "author": {
        "name": "Mykyta Karpin",
        "email": "mkarpin@mirantis.com",
        "time": "Wed Jun 07 13:03:18 2017 +0300"
      },
      "committer": {
        "name": "Mykyta Karpin",
        "email": "mkarpin@mirantis.com",
        "time": "Wed Jun 07 13:05:25 2017 +0300"
      },
      "message": "Fix loopback service status\n\nCurrently when Salt starts setup-loopback-device service\nsystemd executes losetup command and even if it worked\nsuccessfully, systemd marks service as inactive(dead).\nAnd Salt considers service as dead. In order to fix\nthis behavior, we need to add RemainAfterExit\u003dtrue to\nloopback systemd unit template.\n\nOther changes:\n.gitreview added\n\nRelated Prod: https://mirantis.jira.com/browse/PROD-11760\n\nChange-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e\n"
    }
  ]
}