1.4.0 This is the 1.4.0 stable release of ARA. Changes since 1.3.2: API --- - Added support for searching plays, tasks and hosts by name - Added support for searching playbooks by label - Fixed label representation to be consistent through different calls - Reversed the default sort order for playbooks, plays, tasks and results API server ---------- - Validate that settings.yaml (or ARA_SETTINGS) exists before launching (thank you @zswanson!) - Template the default settings file without objects generated by python-box Bundled reporting interface --------------------------- - Added a default robots.txt to prevent crawling - Added support for searching by label - Improved the display of labels in the playbook list - Added pagination support when browsing the playbook report list - Use relative links for pagination (thank you @flowerysong !) - Bumped included patternfly CSS from 2.21.5 to 2.56.3 ara_api Ansible role ------------ - Provide sensible PATH defaults when virtualenvs are not used - Added support for installing from Fedora packages - Only run SQL migrations once when necessary - Allow retries when attempting to run SQL migrations - Ensure settings.yaml permissions are 0640 - Added "ara_api_secure_logging" variable to control behavior of sensitive tasks with no_log - Properly default to IPv6 when no IPv4 is available - Default gunicorn worker count based on number of available CPU cores - Added support for deploying on EL8 Ansible plugins --------------- - New Ansible plugins: ara_playbook and ara_api - Improved consistency of stored task results (thank you @flowerysong!) - Fix bad logic when determining if labels should be updated - Added support for not saving files based on patterns (thank you @LaurentDumont!) - Added support for specifying default playbook labels Integration tests ----------------- - Refactored integration tests to simplify and improve coverage across different database backends, linux distributions and versions of Ansible Upgrade notes ------------- - 1.4 introduces a new SQL migration to ensure labels are unique. If upgrading from a previous version, you will need to run SQL migrations with ``ara-manage migrate``.