{"push_id":2705797837,"size":5,"distinct_size":2,"ref":"refs/heads/inventory","head":"06c3acdd69355e3af24a1f479005ea83e42e0d81","before":"5651ddc8b335f779f54adcb545123b5a4923f58c","commits":[{"sha":"fdcbe29d3fc293d74c46e0929261303da65a18b8","author":{"name":"Alexander Braverman","email":"2499c0a373a0984319a1fdb58d761e52a05e83da@redhat.com"},"message":"refactor verification tests\n\nOriginal tests:\nroles/pulp3/molecule/default/tests/test_default.py","distinct":false,"url":"https://api.github.com/repos/Ichimonji10/ansible-pulp3/commits/fdcbe29d3fc293d74c46e0929261303da65a18b8"},{"sha":"5decbccec2f6ac4d9c4cafdba275219c89ad07c8","author":{"name":"Alexander Braverman","email":"2499c0a373a0984319a1fdb58d761e52a05e83da@redhat.com"},"message":"Remove meaningless assertion","distinct":false,"url":"https://api.github.com/repos/Ichimonji10/ansible-pulp3/commits/5decbccec2f6ac4d9c4cafdba275219c89ad07c8"},{"sha":"7f184bdf9170006138b921ca598a8b15cc2c4a1d","author":{"name":"Jared Wilkerson","email":"df2960299ca143ae778ce171a1b4f34af543a97c@redhat.com"},"message":"Rewrite pulp 3 database tasks\n\nThe pulp 3 database tasks are non-idempotent:\n\n* When the `pulp_database_migrate` variable is true, several database\n  migrations commands run, and when these database migrations commands\n  run, they always return a \"changed\" status. Fix this by doing two\n  things:\n\n  * Drop this variable, and always run database migrations. There's no\n    harm in repeatedly running them.\n  * Only report a \"changed\" status when the migrations runner reports\n    than something has changed.\n\n* Do not report a \"changed\" status when setting the Pulp admin user's\n  password. This isn't ideal, as this task might actually change the\n  Pulp admin user's password! But there's no good known solution for\n  finding out whether this task changes the state of the target host,\n  and letting this reporting bug slide allows us to move forward with\n  other goals.\n\nAlso:\n\n* Apply \"become\" to certain tasks, so that they no longer implicitly\n  rely on the Ansible user being root, or otherwise having certain\n  permissions.\n* Find the pulpcore install directory using the \"find\" module instead of\n  the \"shell\" module, and explicitly assert that this directory was\n  found. This is a much more robust solution than relying on the\n  vagaries of the target system, such as which directories are matched\n  by the shell's globbing, and the features of the shell the happens to\n  be chosen by Ansible.\n* Change the molecule playbook's Pulp admin password from '' to 'admin.'\n  This allows the molecule playbook to succeed: one cannot set an empty\n  string as the Pulp admin password.\n* Drop the default `pulp_default_admin_password`. There's no possible\n  sane default value for a secret, so why provide a default one?","distinct":false,"url":"https://api.github.com/repos/Ichimonji10/ansible-pulp3/commits/7f184bdf9170006138b921ca598a8b15cc2c4a1d"},{"sha":"f536d122d3b25d61c622bdaef7b663dd149d281b","author":{"name":"Jared Wilkerson","email":"df2960299ca143ae778ce171a1b4f34af543a97c@redhat.com"},"message":"Create pulp3-resource-manager role\n\nWhen executed, this role will install and configure the pulp resource\nmanager service, and will set the state of the service as described by\nthe `pulp_resource_manager_{state,enabled}` variables. (These variables\nhave default values.)\n\nSee: https://pulp.plan.io/issues/3730","distinct":true,"url":"https://api.github.com/repos/Ichimonji10/ansible-pulp3/commits/f536d122d3b25d61c622bdaef7b663dd149d281b"},{"sha":"06c3acdd69355e3af24a1f479005ea83e42e0d81","author":{"name":"Jeremy Audet","email":"a185f7ad4bb01d029b88d05d446d324517c27918@protonmail.com"},"message":"DO NOT MERGE: Add inventory file and vars","distinct":true,"url":"https://api.github.com/repos/Ichimonji10/ansible-pulp3/commits/06c3acdd69355e3af24a1f479005ea83e42e0d81"}]}
{"actor":{"display_login":"Ichimonji10"}}